From: Chris Wedgwood <chris@cybernet.co.nz>
To: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>,
Richard Gooch <Richard.Gooch@atnf.CSIRO.AU>
Cc: Dean Gaudet <dgaudet-list-linux-kernel@arctic.org>,
"Eric W. Biederman" <ebiederm+eric@npwt.net>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Thread implementations...
Date: Fri, 26 Jun 1998 09:24:30 +1200 [thread overview]
Message-ID: <19980626092430.C2759@caffeine.ix.net.nz> (raw)
In-Reply-To: <199806251132.MAA00848@dax.dcs.ed.ac.uk>; from Stephen C. Tweedie on Thu, Jun 25, 1998 at 12:32:35PM +0100
> Not necessarily; we may be able to detect a lot of the relevant access
> patterns ourselves. Ingo has had a swap prediction algorithm for a
> while, and we talked at Usenix about a number of other things we can do
> to tune vm performance automatically. 2.3 ought to be a great deal
> better. madvise() may still have merit, but we really ought to be
> aiming at making the vm system as self-tuning as possible.
madvise(2) will _always_ have some uses.
Large database applications and stuff can know in advance how to tune mmap
regions and stuff. The kernel will always be second guessing here, and
making sub optimal decisions, whereas the application can and probably does
know better.
The same argument also applies to raw devices (but lets not start that
thread again).
-Chris
next prev parent reply other threads:[~1998-06-25 21:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199806240915.TAA09504@vindaloo.atnf.CSIRO.AU>
[not found] ` <Pine.LNX.3.96dg4.980624025515.26983E-100000@twinlark.arctic.org>
[not found] ` <199806241213.WAA10661@vindaloo.atnf.CSIRO.AU>
1998-06-24 22:00 ` Eric W. Biederman
1998-06-24 23:41 ` Richard Gooch
1998-06-25 4:45 ` Eric W. Biederman
1998-06-25 17:14 ` Todd Larason
1998-06-26 7:53 ` Christoph Rohland
1998-06-26 14:16 ` Eric W. Biederman
1998-06-29 10:19 ` Stephen C. Tweedie
1998-06-30 6:19 ` Eric W. Biederman
1998-06-30 13:10 ` Stephen C. Tweedie
1998-06-30 19:35 ` Dean Gaudet
1998-07-01 9:09 ` Stephen C. Tweedie
1998-06-25 4:12 ` Dean Gaudet
1998-06-25 3:53 ` Richard Gooch
1998-06-25 11:32 ` Stephen C. Tweedie
1998-06-25 21:24 ` Chris Wedgwood [this message]
1998-06-25 22:16 ` Richard Gooch
1998-06-25 4:56 ` Eric W. Biederman
1998-06-25 11:35 ` Stephen C. Tweedie
1998-06-25 20:31 ` Dean Gaudet
1998-06-30 6:40 ` Eric W. Biederman
1998-06-30 19:30 Larry McVoy
1998-07-01 8:50 ` Stephen C. Tweedie
1998-07-03 15:21 ` Rik van Riel
1998-07-03 20:05 ` Stephen C. Tweedie
1998-07-03 20:36 ` Rik van Riel
1998-07-04 16:37 ` Stephen C. Tweedie
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=19980626092430.C2759@caffeine.ix.net.nz \
--to=chris@cybernet.co.nz \
--cc=Richard.Gooch@atnf.CSIRO.AU \
--cc=dgaudet-list-linux-kernel@arctic.org \
--cc=ebiederm+eric@npwt.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
/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