| 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
| ||
|
Date: Thu, 12 Jun 2008 13:29:52 -0400 From: Rik van Riel <riel@...hat.com> To: Nick Piggin <nickpiggin@...oo.com.au> Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Lee Schermerhorn <lee.schermerhorn@...com>, Kosaki Motohiro <kosaki.motohiro@...fujitsu.com>, linux-mm@...ck.org, Eric Whitney <eric.whitney@...com> Subject: Re: [PATCH -mm 14/24] Ramfs and Ram Disk pages are unevictable On Thu, 12 Jun 2008 10:54:18 +1000 Nick Piggin <nickpiggin@...oo.com.au> wrote: > On Thursday 12 June 2008 04:42, Rik van Riel wrote: > > From: Lee Schermerhorn <Lee.Schermerhorn@...com> > > > > Christoph Lameter pointed out that ram disk pages also clutter the > > LRU lists. When vmscan finds them dirty and tries to clean them, > > the ram disk writeback function just redirties the page so that it > > goes back onto the active list. Round and round she goes... > This isn't the case for brd any longer. It doesn't use the buffer > cache as its backing store, so the buffer cache is reclaimable. What does that mean? I know that pages of files that got paged into the page cache from the ramdisk can be evicted (back to the ram disk), but how do the brd pages themselves behave? -- All Rights Reversed -- 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