linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: William Lee Irwin III <wli@holomorphy.com>,
	Marc Singer <elf@buici.com>,
	linux-mm@kvack.org
Subject: Re: Might refill_inactive_zone () be too aggressive?
Date: Sat, 17 Apr 2004 11:44:24 -0700	[thread overview]
Message-ID: <20040417184424.GA4066@flea> (raw)
In-Reply-To: <20040417183325.GN743@holomorphy.com>

On Sat, Apr 17, 2004 at 11:33:25AM -0700, William Lee Irwin III wrote:
> On Sat, Apr 17, 2004 at 11:10:42AM -0700, William Lee Irwin III wrote:
> >> I'm not sure it's expected. Maybe this patch fares better?
> 
> On Sat, Apr 17, 2004 at 11:28:38AM -0700, Marc Singer wrote:
> > Ah, that's a much different thing.  That works for me.  Is that
> > something you'd want to put into the kernel?
> 
> Since we have a coherent story about this working for you, I think
> we should probably send it upstream for review. I don't have a
> particular opinion about it being the right thing to do, as since it's
> a policy decision, it's rather arbitrary.
> 
> If this is important to you, it may help to numerically quantify your
> results, e.g. some before/after benchmark/throughput/whatever numbers.

That's a difficult thing to do.  My test setup uses an NFS root and
the IO is over NFS.  Due to some oddities in the NFS code, performance
is variable to a degree that does not make for good timing
comparisons.  I'm looking for a way to enable TCP nfsroot mounts.
Once this is working, I may be able to get some reliable numbers.

It's your call about waiting for performance numbers.  As soon as I
have better data, I'll post it.  Setting the swappiness flag does
work, so I can give my users something for now.  It is possible that
this will work for all cases that I'm ever going to see.  Setting
swappiness to zero and the user mapping 50% of RAM will once again
cause reclaim_mapped to go into action.  The difference is that with
swappiness of 60, I'm not allowed to keep any mapped pages in RAM.  At
swappiness of 0, I'm allows to keep half of total RAM mapped.

Cheers.
--
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>

  reply	other threads:[~2004-04-17 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17  6:09 Marc Singer
2004-04-17  6:18 ` William Lee Irwin III
2004-04-17 14:08   ` Marc Singer
2004-04-17 14:21     ` William Lee Irwin III
2004-04-17 17:16     ` William Lee Irwin III
2004-04-17 17:57   ` Marc Singer
2004-04-17 18:10     ` William Lee Irwin III
2004-04-17 18:28       ` Marc Singer
2004-04-17 18:33         ` William Lee Irwin III
2004-04-17 18:44           ` Marc Singer [this message]
2004-04-17 19:19             ` William Lee Irwin III
2004-04-17 19:25               ` Marc Singer
2004-04-17 19:45                 ` 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=20040417184424.GA4066@flea \
    --to=elf@buici.com \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.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