linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sonny Rao <sonny@burdell.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: Memory pressure handling with iSCSI
Date: Tue, 26 Jul 2005 15:31:38 -0400	[thread overview]
Message-ID: <20050726193138.GA32324@kevlar.burdell.org> (raw)
In-Reply-To: <1122403152.6433.39.camel@dyn9047017102.beaverton.ibm.com>

On Tue, Jul 26, 2005 at 11:39:11AM -0700, Badari Pulavarty wrote:
> On Tue, 2005-07-26 at 11:11 -0700, Andrew Morton wrote:
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> > >
> > > After KS & OLS discussions about memory pressure, I wanted to re-do
> > >  iSCSI testing with "dd"s to see if we are throttling writes.  
> > > 
> > >  I created 50 10-GB ext3 filesystems on iSCSI luns. Test is simple
> > >  50 dds (one per filesystem). System seems to throttle memory properly
> > >  and making progress. (Machine doesn't respond very well for anything
> > >  else, but my vmstat keeps running - 100% sys time).
> > 
> > It's important to monitor /proc/meminfo too - the amount of dirty/writeback
> > pages, etc.
> > 
> > btw, 100% system time is quite appalling.  Are you sure vmstat is telling
> > the truth?  If so, where's it all being spent?
> > 
> > 
> 
> Well, profile doesn't show any time in "default_idle". So
> I believe, vmstat is telling the truth.

Badari,

You probably covered this, but just to make sure, if you're on a
pentium4 machine, I usually boot w/ "idle=poll" to see proper idle
reporting because otherwise the chip will throttle itself back and
idle time will be skewed -- at least on oprofile.

Sonny
--
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:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2005-07-26 19:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 17:35 Badari Pulavarty
2005-07-26 18:04 ` Roland Dreier
2005-07-26 18:11 ` Andrew Morton
2005-07-26 18:39   ` Badari Pulavarty
2005-07-26 18:48     ` Andrew Morton
2005-07-26 19:12       ` Andrew Morton
2005-07-26 20:36         ` Badari Pulavarty
2005-07-26 21:11         ` Badari Pulavarty
2005-07-26 21:24           ` Andrew Morton
2005-07-26 21:45             ` Badari Pulavarty
2005-07-26 22:10               ` Andrew Morton
2005-07-26 22:48                 ` Badari Pulavarty
2005-07-26 23:07                   ` Andrew Morton
2005-07-26 23:26                     ` Badari Pulavarty
2005-07-27  0:31                       ` Andrew Morton
2005-07-27  1:20                         ` Martin J. Bligh
2005-07-27  1:26                           ` Andrew Morton
2005-07-27  1:47                             ` Martin J. Bligh
2005-07-27  1:31                         ` Badari Pulavarty
2005-07-27  1:40                           ` Andrew Morton
2005-07-26 19:31     ` Sonny Rao [this message]
2005-07-26 20:37       ` Badari Pulavarty
2005-07-26 21:21         ` Andrew Morton
2005-07-26 20:59 ` Rik van Riel
2005-07-26 21:05   ` Badari Pulavarty
2005-07-26 21:33     ` Martin J. Bligh
2005-07-26 22:05       ` Adam Litke
2005-07-26 21:12   ` Andrew Morton

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=20050726193138.GA32324@kevlar.burdell.org \
    --to=sonny@burdell.org \
    --cc=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