| 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
| ||
|
Message-Id: <200806130508.19661.nickpiggin@yahoo.com.au> Date: Fri, 13 Jun 2008 05:08:19 +1000 From: Nick Piggin <nickpiggin@...oo.com.au> To: Lee Schermerhorn <Lee.Schermerhorn@...com> Cc: Rik van Riel <riel@...hat.com>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] undo the brd.c part of ramfs-and-ram-disk-pages-are-unevictable.patch On Friday 13 June 2008 05:00, Lee Schermerhorn wrote: > On Thu, 2008-06-12 at 13:53 -0400, Rik van Riel wrote: > > Undo the brd.c part of ramfs-and-ram-disk-pages-are-unevictable.patch. > > The brd pages do not live on the LRU at all, so there is no need to > > play these tricks. > > Does this mean that these pages cannot be migrated? E.g., to evacuate > memory for hotplug? Looks like all paths to migrate_pages() construct a > list of pages to migrate by isolating them from the lru > [isolate_lru_page()]. Any pages not found in the lru are skipped. Yes. They have nothing to do with user pages or pagecache pages at all really. brd is now a properly layered block device driver that does not know anything about buffer cache ;) You can think of the pages it allocates as completely private, and they are used to implement the backing store for the block device. The vm/fs layers will instantiate buffer cache over this device, which is reclaimable. -- 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