public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Burton" <burton@tailrank.com>
To: "Rik van Riel" <riel@redhat.com>
Cc: "FD Cami" <francois.cami@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Ability to limit or disable page caching?
Date: Mon, 5 May 2008 14:00:51 -0700	[thread overview]
Message-ID: <30c6373b0805051400jebd4132ob23ec38bdf1ccb93@mail.gmail.com> (raw)
In-Reply-To: <20080505164446.2ec9a543@cuia.bos.redhat.com>

> One of the problems is that the process pages (anonymous memory) and
> page cache pages live on the same LRU, so the kernel cannot always
> easily find the page cache pages when it is trying to evict something.

Ah... that makes sense.

> Once that is fixed, and replacement is biased towards evicting page
> cache pages, the system may do the right thing by itself.

Yeah.  That seems like it...

> I have no such tunable in my code (yet), because I would like the
> kernel to do the right thing automatically.  I will post a 2.6.25 based
> kernel RPM for Fedora 9 soon with the split LRU patch series applied.

With the same patch you linked to above?  No new code..

We're on Debian so I need to dive in and see how easy it would be for
us to compile our own kernel.

I've done it in the past but I've avoided running anything non-stock
for about 2 years now...

We're on 2.6.24 though but that's not a big issue.

> If you feel like testing/breaking it, I would be interested to see if
> it does indeed do the right thing for your workload or if it needs more
> tuning.

Well we'd be deploying it in product :).. what's the ETA into making
it into the official kernel?

Kevin


-- 
Founder/CEO Tailrank.com
Location: San Francisco, CA
AIM/YIM: sfburtonator
Skype: burtonator
Work: http://spinn3r.com and http://tailrank.com
Blog: http://feedblog.org
Cell: 415-637-8078
Fax: 1-415-358-419 PIN: 0092

  reply	other threads:[~2008-05-05 21:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  7:12 Ability to limit or disable page caching? Kevin Burton
2008-05-05 11:16 ` FD Cami
2008-05-05 18:34   ` Kevin Burton
2008-05-05 19:28     ` FD Cami
2008-05-05 19:42       ` Kevin Burton
2008-05-05 20:10         ` Andi Kleen
2008-05-05 20:28           ` Kevin Burton
2008-05-05 20:31             ` Kevin Burton
2008-05-05 20:40               ` Kevin Burton
2008-05-06  0:23                 ` Andi Kleen
2008-05-06  0:30                   ` Kevin Burton
2008-05-05 21:24           ` Bernd Eckenfels
2008-05-05 20:44         ` Rik van Riel
2008-05-05 21:00           ` Kevin Burton [this message]
2008-05-05 22:08             ` Rik van Riel
2008-05-05 22:15               ` Kevin Burton
2008-05-08  2:08             ` split LRU kernel RPM Rik van Riel
2008-05-05 21:03           ` Ability to limit or disable page caching? Chris Friesen
2008-05-05 21:32             ` Kevin Burton
2008-05-05 22:06               ` Rik van Riel
2008-05-06 11:02       ` Tomasz Kłoczko
2008-05-05 19:33     ` Kevin Burton

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=30c6373b0805051400jebd4132ob23ec38bdf1ccb93@mail.gmail.com \
    --to=burton@tailrank.com \
    --cc=francois.cami@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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