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: <20140727010144.GA13438@thunk.org> Date: Sat, 26 Jul 2014 21:01:44 -0400 From: Theodore Ts'o <tytso@....edu> To: Peter Zijlstra <peterz@...radead.org>, Gioh Kim <gioh.kim@....com>, Alexander Viro <viro@...iv.linux.org.uk>, Andrew Morton <akpm@...ux-foundation.org>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Andreas Dilger <adilger.kernel@...ger.ca>, linux-ext4@...r.kernel.org Subject: Re: [PATCH 0/2] new API to allocate buffer-cache for superblock in non-movable area Gioh, As follow up, if you want some further discussions about why these patches should be accepted, it would be good to get some hard data about why the keeping the ext4 superblock pinned is causing such a problem for page migation. Can you give us more details about what the impact is of not having these patches? And how it compres to other data structures which are currently allocated in the moveable area and tend to be pinned effectively indefinitely? Thanks, - Ted -- 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