linux-kernel - Re: [PATCH 0/2] new API to allocate buffer-cache for superblock in non-movable area

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140801160415.GD9918@twins.programming.kicks-ass.net>
Date:	Fri, 1 Aug 2014 18:04:15 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jan Kara <jack@...e.cz>
Cc:	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>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org, linux-mm@...ck.org,
	Minchan Kim <minchan@...nel.org>,
	Joonsoo Kim <js1304@...il.com>
Subject: Re: [PATCH 0/2] new API to allocate buffer-cache for superblock in
 non-movable area

On Fri, Aug 01, 2014 at 05:24:59PM +0200, Jan Kara wrote:

>   OK, makes sense. But then if there's heavy IO going on, anything that has
> IO pending on it is pinned and IO completion can easily take something
> close to a second or more. So meeting subsecond deadlines may be tough even
> for ordinary data pages under heavy load, even more so for metadata where
> there are further constraints. OTOH phones aren't usually IO bound so in
> practice it needn't be so bad ;). 

Yeah, typically phones are not IO bound :-)

> So if it is sub-second unless someone
> loads the storage, then that sounds doable even for metadata. But we'll
> need to attach ->migratepage callback to blkdev pages and at least in ext4
> case teach it how to move pages tracked by the journal.

Right, making it possible at all if of course much prefered over not
possible, regardless of timeliness :-)

> > Sadly its not only mobile devices that excel in crappy hardware, there's
> > plenty desktop stuff that could use this too, like some of the v4l
> > devices iirc.
>   Yeah, but in such usecases the guarantees we can offer for completion of
> migration are even more vague :(.

Yeah, lets start by making it possible, after that we can maybe look at
making it better, who knows.

Content of type "application/pgp-signature" skipped