From: Andrea Arcangeli <andrea@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Johannes Erdfelt <johannes@erdfelt.com>,
Mark Hahn <hahn@physics.mcmaster.ca>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.19rc2aa1 VM too aggressive?
Date: Wed, 24 Jul 2002 00:41:17 +0200 [thread overview]
Message-ID: <20020723224117.GP1117@dualathlon.random> (raw)
In-Reply-To: <1027460087.14636.102.camel@dell_ss3.pdx.osdl.net>
On Tue, Jul 23, 2002 at 02:34:46PM -0700, Stephen Hemminger wrote:
> On Tue, 2002-07-23 at 13:33, Andrea Arcangeli wrote:
>
> > some seldom swapout is ok, the strange thing are those small
> > swapins/swapouts. I also assume it's writing using write(2), not with
> > map_shared+msync.
>
> I am using ben's lahaise new AIO which effectively maps the pages in
> before the i/o. Using normal I/O I don't see swapping, the cached peaks
> at about .827028
sorry I thought you were using 2.4.19rc3aa1, -ac reintroduces a number
of vm bugs with the rmap vm that I fixed some age ago, plus it
underperformns in many areas, and about async-io I'm not shipping it.
You should report this to Alan and Ben. I'm interested only about
problems that can be reproduced with mainline and -aa, thanks.
> > can you try:
> >
> > echo 1000 >/proc/sys/vm/vm_mapped_ratio
>
> That file does not exist in 2.4.19rc3ac3
yes I misunderstood the kernel version.
> bash-2.05$ ls /proc/sys/vm
> bdflush max_map_count min-readahead page-cluster
> kswapd max-readahead overcommit_memory pagetable_cache
> >
> > I also wonder if you've quite some amount of mapped address space durign
> > the benchmark. In such case there's no trivial way around it, the vm
> > will constantly found tons of mapped address space, and it will trigger
> > some swapouts, however the swapins shouldn't happen so fast in such
> > case.
> The AIO will pin some space, but the upper bound should be
> NIO(16) * Record Size(64k) = 1 Meg
>
>
> > In any case the sysctl will allow you to tune for your workload.
> >
> > Andrea
>
Andrea
next prev parent reply other threads:[~2002-07-23 22:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 20:33 2.4.19rc2aa1 VM too aggressive? Johannes Erdfelt
2002-07-19 20:52 ` David Rees
2002-07-19 21:03 ` Johannes Erdfelt
[not found] ` <Pine.LNX.4.33.0207191722260.6698-100000@coffee.psychology.mcmaster.ca>
2002-07-19 21:45 ` Johannes Erdfelt
2002-07-23 19:48 ` Andrea Arcangeli
2002-07-23 20:22 ` Stephen Hemminger
2002-07-23 20:33 ` Andrea Arcangeli
2002-07-23 21:34 ` Stephen Hemminger
2002-07-23 22:41 ` Andrea Arcangeli [this message]
2002-07-19 22:32 ` Austin Gonyou
2002-07-19 23:04 ` Johannes Erdfelt
2002-07-19 23:27 ` J Sloan
2002-07-20 2:12 ` Austin Gonyou
2002-07-20 0:07 ` Rik van Riel
2002-07-23 23:52 ` Andrea Arcangeli
2002-07-24 0:21 ` Rik van Riel
2002-07-24 4:49 ` Austin Gonyou
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=20020723224117.GP1117@dualathlon.random \
--to=andrea@suse.de \
--cc=hahn@physics.mcmaster.ca \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.