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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 26 Jul 2014 21:01:44 -0400
From:	Theodore Ts'o <>
To:	Peter Zijlstra <>, Gioh Kim <>,
	Alexander Viro <>,
	Andrew Morton <>,
	"Paul E. McKenney" <>,
	Jan Kara <>,,,
	Andreas Dilger <>,
Subject: Re: [PATCH 0/2] new API to allocate buffer-cache for superblock in
 non-movable area


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?


						- Ted
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists