On Wed, Dec 20 2006, Kiyoshi Ueda wrote:
> Hi Jens,
>
> Sorry for the less explanation.
>
> On Wed, 20 Dec 2006 14:49:24 +0100, Jens Axboe <[email protected]> wrote:
> > On Tue, Dec 19 2006, Kiyoshi Ueda wrote:
> > > This patch adds new "end_io_first" hook in __end_that_request_first()
> > > for request-based device-mapper.
> >
> > What's this for, lack of stacking?
>
> I don't understand the meaning of "lack of stacking" well but
> I guess that it means "Is the existing hook in end_that_request_last()
> not enough?" If so, the answer is no.
> (If the geuss is wrong, please let me know.)
>
> The new hook is needed for error handling in dm.
> For example, when an error occurred on a request, dm-multipath
> wants to try another path before returning EIO to application.
> Without the new hook, at the point of end_that_request_last(),
> the bios are already finished with error and can't be retried.
Ok, I see what you are getting at. The current ->end_io() is called when
the request has fully completed, you want notification for each chunk
potentially completed.
I think a better design here would be to use ->end_io() as the full
completion handler, similar to how bio->bi_end_io() works. A request
originating from __make_request() would set something ala:
int fs_end_io(struct request *rq, int error, unsigned int nr_bytes)
{
if (!__end_that_request_first(rq, err, nr_bytes)) {
end_that_request_last(rq, error);
return 0;
}
return 1;
}
and normal io completion from a driver would use a helper:
int blk_complete_io(struct request *rq, int error, unsigned int nr_bytes)
{
return rq->end_io(rq, error, nr_bytes);
}
instead of calling the functions manually. That would allow you to get
notification right at the beginning and do what you need, without adding
a special hook for this.
When designing these things, never be afraid to change some of the core
bits. It is a lot better than hacking around the current code, if it
doesn't quite fit your needs.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
