From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Frank Dekervel <Frank.dekervel@student.kuleuven.ac.Be>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: need help interpreting 'free' output.
Date: Tue, 30 Oct 2001 18:06:16 +0100 [thread overview]
Message-ID: <20011030180616.M1340@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.21.0110301557560.1229-100000@localhost.localdomain> <Pine.LNX.4.33.0110300839360.8603-200000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110300839360.8603-200000@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Oct 30, 2001 at 08:52:58AM -0800
On Tue, Oct 30, 2001 at 08:52:58AM -0800, Linus Torvalds wrote:
> So in the short range, I haven't come up with any really good approaches,
> but I suspect I'll just have to move the shrink_[di]cache() back to the
> caller, which will at least shrink them on swapouts (a bit too much, I
> think, but on the other hand maybe not).
Agreed.
It is still interesting to hear if it makes a big performance differece
under swap though. In particular it would be very nice to keep inodes
with pagecache in it out of the unused-inode-list, but it would need
additional bitkeeping in inode.c.
I'm also wondering why you dropped the early-cow for the write swapins,
just to avoid managing the anon pages in the lru in do_swap_page and to
have the logic only in once place? I kept the early-cow logic so I only
get 1 page fault for every write-swapped-in pages.
Andrea
next prev parent reply other threads:[~2001-10-30 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 11:32 need help interpreting 'free' output Frank Dekervel
2001-10-30 11:46 ` Mike Fedyk
2001-10-30 14:02 ` Frank Dekervel
2001-10-30 16:07 ` Hugh Dickins
2001-10-30 16:51 ` Andrea Arcangeli
2001-10-30 16:52 ` Linus Torvalds
2001-10-30 17:06 ` Andrea Arcangeli [this message]
2001-10-30 17:28 ` Linus Torvalds
2001-10-30 17:39 ` Andrea Arcangeli
2001-10-30 17:53 ` Linus Torvalds
2001-10-30 18:16 ` Andrea Arcangeli
2001-10-30 18:28 ` Linus Torvalds
2001-10-30 18:58 ` Andrea Arcangeli
2001-10-30 19:21 ` Linus Torvalds
2001-10-30 20:05 ` Andrea Arcangeli
2001-10-30 20:25 ` Linus Torvalds
2001-10-30 18:05 ` Eric W. Biederman
2001-10-30 20:47 ` David S. Miller
2001-10-30 18:11 ` Frank Dekervel
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=20011030180616.M1340@athlon.random \
--to=andrea@suse.de \
--cc=Frank.dekervel@student.kuleuven.ac.Be \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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