From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: pre5 VM feedback..
Date: 15 Jan 2001 18:48:32 -0800 [thread overview]
Message-ID: <940cq0$6fe$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A63A9AE.345CBAF3@mandrakesoft.com>
In article <3A63A9AE.345CBAF3@mandrakesoft.com>,
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>$!@#@! pre6 is already out :)
Yes, and for heavens sake don't use it, because the reiserfs merge got
some dirty inode logic wrong. pre7 fixes just that one line and should
be ok again.
>Anyway, this may be a totally subjective (and incorrect) perception, but
>it seems to me like the recent 2.4.x-test kernels and thereafter start
>swapping things out really quickly. Case in point: "diff -urN
>linux.vanilla linux" command swaps out Konqueror and Netscape Mail, even
>though I was using them only a few minutes ago.
Yes. It's really nice for some stuff, but a bit too aggressive for
normal use, I think.
If you want to play with tuning, I'd suggest something like
- make SWAP_SHIFT bigger (try with 7 instead of 5)
- do the "self-swap-out" only for __GFP_VM allocations, and add the
__GFP_VM flag to all page fault allocations (ie __GPF_VM would be a
flag that says "this allocation will grow my RSS").
The latter is kind of debatable - some allocations can't easily be put
in one category or the other (ie page cache growing - do we do it
because of the page cache or because we want to map the page?)
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-16 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 1:53 pre5 VM feedback Jeff Garzik
2001-01-16 2:48 ` Linus Torvalds [this message]
2001-01-16 3:03 ` Jeff Garzik
2001-01-16 3:20 ` Linus Torvalds
2001-01-16 3:43 ` Aaron Sethman
2001-01-19 5:51 ` Marcelo Tosatti
2001-01-19 5:57 ` Marcelo Tosatti
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='940cq0$6fe$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.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.