public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Shailabh Nagar <nagar@us.ibm.com>
Cc: Martin Frey <frey@scs.ch>, "'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 20:10:10 +0200	[thread overview]
Message-ID: <20011023201010.D12005@suse.de> (raw)
In-Reply-To: <OF98236159.2E4369EA-ON85256AEE.004D5B64@pok.ibm.com>
In-Reply-To: <OF98236159.2E4369EA-ON85256AEE.004D5B64@pok.ibm.com>

On Tue, Oct 23 2001, Shailabh Nagar wrote:
> >On Tue, Oct 23 2001, Martin Frey wrote:
> >> >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.
> >> >
> >> Yes, it used kiobufs to get a gatherlist, setup a gather DMA out
> >> of that list and submitted it to the SCSI layer. Depending on
> >> the controller 1 MB could be transfered with 0 memcopies, 1 DMA,
> >> 1 interrupt. 200 MB/s with 10% CPU load was really impressive.
> >
> >Let me repeat that the only difference between the kiobuf and the
> >current approach is the overhead incurred on multiple __make_request
> >calls. Given the current short queues, this isn't as bad as it used to
> >be. Of course it isn't free, though.
> 
> The patch below attempts to address exactly that - reducing the number of
> submit_bh/__make_request() calls made for raw I/O. The basic idea is to do
> a major
> part of the I/O in page sized blocks.
> 
> Comments on the idea ?

Looks fine to me.

-- 
Jens Axboe


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 14:12 [Lse-tech] Re: Preliminary results of using multiblock raw I/O Shailabh Nagar
2001-10-23 18:10 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-23 14:05 Shailabh Nagar
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=20011023201010.D12005@suse.de \
    --to=axboe@suse.de \
    --cc=baettig@scs.ch \
    --cc=frey@scs.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=nagar@us.ibm.com \
    /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