lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1158323645.12076.9.camel@kleikamp.austin.ibm.com>
Date:	Fri, 15 Sep 2006 07:34:05 -0500
From:	Dave Kleikamp <shaggy@...tin.ibm.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Sandeep Kumar <sandeepksinha@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Efficient Use of the Page Cache with 64 KB Pages

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ