linux-kernel - Re: [PATCH] as-iosched: fix write batch start point

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] [day] [month] [year] [list]

Message-ID: <20071205101548.GB4969@kernel.dk>
Date:	Wed, 5 Dec 2007 11:15:48 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Aaron Carroll <aaronc@...ato.unsw.edu.au>,
	linux-kernel@...r.kernel.org,
	Peter Chubb <peterc@...ato.unsw.edu.au>
Subject: Re: [PATCH] as-iosched: fix write batch start point

On Wed, Dec 05 2007, Nick Piggin wrote:
> On Wed, Dec 05, 2007 at 09:07:07PM +1100, Aaron Carroll wrote:
> > New write batches currently start from where the last one completed.
> > We have no idea where the head is after switching batches, so this
> > makes little sense.  Instead, start the next batch from the request
> > with the earliest deadline in the hope that we avoid a deadline
> > expiry later on.
> > 
> > Signed-off-by: Aaron Carroll <aaronc@...ato.unsw.edu.au>
> 
> I think this seems reasonable. What's deadline doing in this case?
> They should probably be kept in synch where possible...

Aaron sent a similar patch for deadline a while ago, so this just
matches them up again. I acked that patch, it makes a lot of sense to
me.

-- 
Jens Axboe

--
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/