From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: plugging in 2.4. Does it work?
Date: Wed, 21 Feb 2001 16:36:32 +0100 (MET) [thread overview]
Message-ID: <200102211536.f1LFaWZ03985@oboe.it.uc3m.es> (raw)
"Jens Axboe wrote:"
> It will still cluster, the code above checks if the next bh is
> contigious -- if it isn't, then check if we can grow another segment.
> So you may be lucky that some buffer_heads in the chain are indeed
> contiguous, that's what the segment count is for. This is exactly
> the same in 2.4.
OK .. that fixed it. Turned out that I wasn't walking the request bh's
on read of clustered requests (but I was doing so on write).
Reads now work fine, but writes show signs of having some problem. I'll
beat on that later.
I'm particularly concerned about the error behaviour. How should I set
up the end_request code in the case when the request is to be errored?
Recall that my end_request code is presently like this:
io_spin_lock
while (end_that_request_first(req,!req->errors);
// one more time for luck
if (!end_that_request_first(req,!req->errors)
end_that_request_last(req);
io_spin_unlock
and I get the impression from other driver code snippets that a single
end_that_request_first is enough, but looking at the implementation it
can't be. It looks from ll_rw_blk that I should walk the bh chain just
the same in the case of error, no?
Peter
next reply other threads:[~2001-02-21 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 15:36 Peter T. Breuer [this message]
2001-02-21 17:27 ` Jens Axboe
2001-02-21 17:54 ` Peter T. Breuer
-- 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=200102211536.f1LFaWZ03985@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--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®