Subject: Re: [RFC][PATCH] Move bv_offset/bv_len update after bio_endio in
	__end_that_request_first
From: Christophe Saout <christophe@saout.de>
To: Jens Axboe <axboe@suse.de>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@osdl.org>
In-Reply-To: <1073048438.4239.10.camel@leto.cs.pocnet.net>
References: <20040101173214.GA4496@leto.cs.pocnet.net>
	 <20040102104637.GN5523@suse.de>
	 <1073048438.4239.10.camel@leto.cs.pocnet.net>
Content-Type: text/plain
Message-Id: <1073049978.4239.14.camel@leto.cs.pocnet.net>
Mime-Version: 1.0
Date: Fri, 02 Jan 2004 14:26:18 +0100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 947
Lines: 24

Am Fr, den 02.01.2004 schrieb Christophe Saout um 14:00:

> > > That's why I need to know exactly how many and which  bvecs were completed
> > > in my bi_end_io function.
> > > 
> > > Or do you think it is safer to count backwards using bi_vcnt and bi_size?
> > 
> > I'm inclined to thinking that, indeed. Those two fields have a more well
> > established usage, so I think you'll be better off doing that in the
> > long run.
> 
> Ok, if you say so. This and the IDE multwrite thing are the only two
> places in the kernel preventing bi_idx to be usable this way. I just
> thought it was nicer.

... but I still need bv_offset and bv_len to be unchanged in the
bio_endio call. Can we please do this?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/