mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Sandeep Kumar <sandeepksinha@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Efficient Use of the Page Cache with 64 KB Pages
Date: Fri, 15 Sep 2006 07:34:05 -0500	[thread overview]
Message-ID: <1158323645.12076.9.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <1158311488.23551.4.camel@twins>

On Fri, 2006-09-15 at 11:11 +0200, Peter Zijlstra wrote:
> On Fri, 2006-09-15 at 01:50 -0700, Sandeep Kumar wrote:
> > Hey all,
> > I am a newbie and I just read a document with the idea for changes in
> > page cache management for 64 Bit machines. This has been taken from
> > Linux symposium 2006, ottawa.
> > 
> > In order for 64-bit processors to efficiently use large address spaces
> > while maintaining lower TLB miss rates, the Linux kernel can be
> > configured with base page sizes up to 64 KB. While this benefits
> > access to large memory segments and files, it greatly reduces the
> > number of smaller files that can be resident in memory at one time.
> > The idea proposes a change to the Linux kernel to allow file data to
> > be more efficiently stored in memory when the size of the file, or the
> > data at the end of a file, is significantly smaller than the page
> > size.
> > 
> > So, how far is this feature feasible for the linux main line kernel ?
> 
> Not in the form last presented, but Dave is still working on making it
> look pretty and covering more use-cases AFAIK.

Right, I've been sidetracked with some other things, but I'm hoping to
get back on it soon.

> But even then, it will not fix all scenarios...

Right, you'll probably never be able to mmap to a "tail page".   I'm
actually trying a couple different approaches to compare the trade-off
between performance and intrusiveness.  On the less intrusive end, data
would be copied into a smaller buffer after it is read into a full page.
The more ambitious approach would have the smaller buffers aligned to
the sector size (and sized to the block size), and data is read, and
sometimes written, directly into them.

> > Is, this feature already supported ?
> 
> No it is not. 
> 
> In future it would be nice to add the author(s) to the CC list ;-)

Peter, thanks for cc'ing me.

Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2006-09-15 12:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  8:50 Sandeep Kumar
2006-09-15  9:11 ` Peter Zijlstra
2006-09-15 12:34   ` Dave Kleikamp [this message]
2006-09-19 18:38 ` Christoph Lameter
2006-09-19 22:55   ` Tony Luck
2006-09-20  4:29     ` Christoph Lameter

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=1158323645.12076.9.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeepksinha@gmail.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

all inboxes | Powered by JetHome®