mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shailabh Nagar" <nagar@us.ibm.com>
To: Jens Axboe <axboe@suse.de>
Cc: Reto Baettig <baettig@scs.ch>,
	lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] Re: Preliminary results of using multiblock raw I/O
Date: Tue, 23 Oct 2001 10:05:32 -0400	[thread overview]
Message-ID: <OF74054AB1.2E23D4AC-ON85256AEE.004B503C@pok.ibm.com> (raw)



>On Mon, Oct 22 2001, Shailabh Nagar wrote:
>>
>>
>> Unlike the SGI patch, the multiple block size patch continues to use
buffer
>> heads. So the biggest atomic transfer request that can be seen by a
device
>> driver with the multiblocksize patch is still 1 page.
>
>Not so. Given a 1MB contigious request broken into 256 pages, even if
>submitted in these chunks it will be merged into the biggest possible
>request the lower level driver can handle. This is typically 127kB, for
>SCSI it can be as much as 512kB currently and depending on the SCSI
>driver even more maybe.

My mistake - by device driver I wasn't referring to the lowest level
drivers but also
including the merging functionality.

>
>I haven't seen the SGI rawio patch, but I'm assuming it used kiobufs to
>pass a single unit of 1 meg down at the time. Yes currently we do incur
>significant overhead compared to that approach.
>
> Getting bigger transfers would require a single buffer head to be able to
> point to a multipage buffer or not use buffer heads at all.
> The former would obviously be a major change and suitable only for 2.5
> (perhaps as part of the much-awaited rewrite of the block I/O
>
> Ongoing effort.
>
> subsystem).The use of multipage transfers using a single buffer head
would
> also help non-raw I/O transfers. I don't know if anyone is working along
> those lines.

>It is being worked on.


Could you give some idea as to what are some of the ideas being
discussed/proposed ?
It would be nice to know some of the details as they are being worked on.

Thanks,
Shailabh Nagar





             reply	other threads:[~2001-10-23 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 14:05 Shailabh Nagar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 14:12 Shailabh Nagar
2001-10-23 18:10 ` Jens Axboe
2001-10-22 19:08 Shailabh Nagar
2001-10-23  6:42 ` Jens Axboe
2001-10-23  9:59   ` Martin Frey
2001-10-23 10:02     ` Jens Axboe
2001-10-23 16:23   ` Alan Cox
2001-10-23 17:49     ` Jens Axboe
2001-10-23 18:04       ` Alan Cox

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=OF74054AB1.2E23D4AC-ON85256AEE.004B503C@pok.ibm.com \
    --to=nagar@us.ibm.com \
    --cc=axboe@suse.de \
    --cc=baettig@scs.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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®