From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.12-rc6-mm1 & 2K lun testing
Date: Thu, 16 Jun 2005 13:37:30 -0700 [thread overview]
Message-ID: <20050616133730.1924fca3.akpm@osdl.org> (raw)
In-Reply-To: <1118951458.4301.478.camel@dyn9047017072.beaverton.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> >
> > We seem to be always ooming when allocating scsi command structures.
> > Perhaps the block-level request structures are being allocated with
> > __GFP_WAIT, but it's a bit odd. Which I/O scheduler? If cfq, does
> > reducing /sys/block/*/queue/nr_requests help?
>
> Yes. I am using CFQ scheduler. I changed nr_requests to 4 for all
> my devices. I also changed "min_free_kbytes" to 64M.
Yeah, that monster cfq queue depth continues to hurt in corner cases.
> Response time is still bad. Here is the vmstat, meminfo, slabinfo
> and profle output. I am not sure why profile output shows
> default_idle(), when vmstat shows 100% CPU sys.
(please inline text rather then using attachments)
> MemTotal: 7209056 kB
> ...
> Dirty: 5896240 kB
That's not going to help - we're way over 40% there, so the VM is getting
into some trouble.
Try reducing the dirty limits in /proc/sys/vm by a lot to confirm that it
helps.
There are various bits of slop and hysteresis and deliberate overshoot in
page-writeback.c which are there to enhance IO batching and to reduce CPU
consumption. A few megs here and there adds up when you multiply it by
2000...
Try this:
diff -puN mm/page-writeback.c~a mm/page-writeback.c
--- 25/mm/page-writeback.c~a Thu Jun 16 13:36:29 2005
+++ 25-akpm/mm/page-writeback.c Thu Jun 16 13:36:54 2005
@@ -501,6 +501,8 @@ void laptop_sync_completion(void)
static void set_ratelimit(void)
{
+ ratelimit_pages = 32;
+ return;
ratelimit_pages = total_pages / (num_online_cpus() * 32);
if (ratelimit_pages < 16)
ratelimit_pages = 16;
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-06-16 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:36 Badari Pulavarty
2005-06-15 18:30 ` Nick Piggin
2005-06-15 18:30 ` Badari Pulavarty
2005-06-15 19:02 ` Nick Piggin
2005-06-15 20:56 ` Badari Pulavarty
2005-06-16 1:48 ` Nick Piggin
2005-06-15 23:23 ` Dave Chinner
2005-06-15 21:39 ` Chen, Kenneth W
2005-06-15 22:35 ` Badari Pulavarty
2005-06-16 7:24 ` Andrew Morton
2005-06-16 19:50 ` Badari Pulavarty
2005-06-16 20:37 ` Andrew Morton [this message]
2005-06-16 23:43 ` Badari Pulavarty
2005-06-17 0:51 ` Andrew Morton
2005-06-17 15:10 ` Badari Pulavarty
2005-06-17 21:13 ` Andrew Morton
2005-06-22 0:34 ` 2.6.12-mm1 & 2K lun testing (JFS problem ?) Badari Pulavarty
2005-06-22 1:41 ` William Lee Irwin III
2005-06-22 16:23 ` Badari Pulavarty
2005-06-22 13:50 ` Dave Kleikamp
2005-06-22 16:56 ` Badari Pulavarty
2005-06-22 21:02 ` Badari Pulavarty
2005-06-16 22:42 ` 2.6.12-rc6-mm1 & 2K lun testing William Lee Irwin III
2005-06-16 22:25 ` Badari Pulavarty
2005-06-16 22:58 ` William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050616133730.1924fca3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox