From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "Jens Axboe" <axboe@suse.de>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: plugging in 2.4. Does it work?
Date: Wed, 21 Feb 2001 18:54:38 +0100 (MET) [thread overview]
Message-ID: <200102211754.f1LHscA12507@oboe.it.uc3m.es> (raw)
In-Reply-To: <20010221182743.W1447@suse.de> from "Jens Axboe" at "Feb 21, 2001 06:27:43 pm"
"A month of sundays ago Jens Axboe wrote:"
> The implementation in ll_rw_blk.c (and other places) assumes that
> a failed request just means the first chunk and it then makes sense
> to just end i/o on that buffer and resetup the request for the next
> buffer. If you want to completely scrap the request on an error, then
> you'll just have to do that manually (ie loop end_that_request_first
> and end_that_request_last at the end).
>
> void my_end_request(struct request *rq, int uptodate)
> {
> while (end_that_request_first(rq, uptodate))
> ;
>
> io_lock
> end_that_request_last(rq);
> io_unlock
> }
OK, thanks!
> And why you keep insisting on a duplicate end_that_request_first I don't
> know?!
Backwards compatibility. The code has to keep working under older
kernel versions too in order to pass the regression tests, and the
simplest thing is to put the front while loop in an ifdef while I work
on it. At some stage soon I'll do as you want. Things have stopped
oopsing on write now, and I've sent it for testing.
That's also why I have the io_lock around the whole code instead of
only the last part. I have to put it around something that at least
existed in 2.2 and even 2.0. I've stepped the version number and will
be revising the code while its being tested. But thanks for the
concern :-). I appreciate it!
Peter
next prev parent reply other threads:[~2001-02-21 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 15:36 Peter T. Breuer
2001-02-21 17:27 ` Jens Axboe
2001-02-21 17:54 ` Peter T. Breuer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-20 22:41 Peter T. Breuer
2001-02-20 22:54 ` Jens Axboe
2001-02-20 23:27 ` Peter T. Breuer
2001-02-20 23:37 ` Jens Axboe
2001-02-20 23:48 ` Peter T. Breuer
2001-02-20 23:52 ` Jens Axboe
2001-02-20 22:58 ` Jens Axboe
2001-02-20 23:32 ` Peter T. Breuer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200102211754.f1LHscA12507@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®