From: Jens Axboe <axboe@suse.de>
To: "Peter T. Breuer" <ptb@it.uc3m.es>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: plugging in 2.4. Does it work?
Date: Wed, 21 Feb 2001 00:52:24 +0100 [thread overview]
Message-ID: <20010221005224.C1447@suse.de> (raw)
In-Reply-To: <20010221003757.A1447@suse.de> <200102202348.f1KNmMQ03100@oboe.it.uc3m.es>
In-Reply-To: <200102202348.f1KNmMQ03100@oboe.it.uc3m.es>; from ptb@it.uc3m.es on Wed, Feb 21, 2001 at 12:48:22AM +0100
On Wed, Feb 21 2001, Peter T. Breuer wrote:
> I recall that in 2.2 the make_request code tested that the
> buffers were contiguous in memory. From 2.2.18:
>
> /* Can we add it to the end of this request? */
> if (back) {
> if (req->bhtail->b_data + req->bhtail->b_size
> != bh->b_data) {
> if (req->nr_segments < max_segments)
> req->nr_segments++;
> else break;
> }
>
> It looks to me like it tested that the b_data char* pointers of the
> two requests being considered are exactly distant by the declared
> size of one.
>
> Is that no longer the case? If so, that's my answer.
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.
--
Jens Axboe
next prev parent reply other threads:[~2001-02-20 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 22:41 plugging in 2.4. Does it work? 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 [this message]
2001-02-20 22:58 ` Jens Axboe
2001-02-20 23:32 ` Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 15:36 Peter T. Breuer
2001-02-21 17:27 ` Jens Axboe
2001-02-21 17:54 ` 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=20010221005224.C1447@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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