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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 5 Dec 2007 11:14:34 +0100
From:	Nick Piggin <npiggin@...e.de>
To:	Aaron Carroll <aaronc@...ato.unsw.edu.au>
Cc:	Jens Axboe <jens.axboe@...cle.com>, 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 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...

Acked-by: Nick Piggin <npiggin@...e.de>

> ---
>  block/as-iosched.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/block/as-iosched.c b/block/as-iosched.c
> index 4513fc5..555cd6b 100644
> --- a/block/as-iosched.c
> +++ b/block/as-iosched.c
> @@ -1097,7 +1097,8 @@ dispatch_writes:
>  		ad->batch_data_dir = REQ_ASYNC;
>  		ad->current_write_count = ad->write_batch_count;
>  		ad->write_batch_idled = 0;
> -		rq = ad->next_rq[ad->batch_data_dir];
> +		rq = rq_entry_fifo(ad->fifo_list[REQ_ASYNC].next);
> +		ad->last_check_fifo[REQ_ASYNC] = jiffies;
>  		goto dispatch_request;
>  	}
>  
> -- 
--
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