mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: akpm@zip.com.au, dougg@torque.net, ingo.oeser@informatik.tu-chemnitz.de
Cc: axboe@suse.de, linux-kernel@vger.kernel.org, martin@dalecki.de
Subject: Re: direct-to-BIO for O_DIRECT
Date: Wed, 10 Jul 2002 23:09:53 -0700	[thread overview]
Message-ID: <200207110609.XAA20931@adam.yggdrasil.com> (raw)

Douglas Gilbert wrote:
>Ingo Oeser wrote:
[...]
>> It would be nice if we could just map a set of user pages to a scatterlist.
>
>After disabling kiobufs in sg I would like such a drop
>in replacement.
>
>> Developers of mass transfer devices (video grabbers, dsp devices, sg and
>> many others) would just LOVE you for this ;-)
>
>Agreed. Tape devices could be added to your list.
>Large page support will make for very efficient zero
>copy IO.
>
>> Block devices are the common case worth optimizing for, but character
>> devices just need to reimplement most of this, if they want the same 
>> optimizations. Some devices need mass transfers and are NOT blockdevices.
>
>> Please consider supporting them better for 2.5 in stuff similiar to BIOs
>> and DMA to/from user pages.
>
>CIOs?

	This is what I want to accomplish in my proposal to
pull most of the DMA transfer optimization code up from block
devices by generalizing DMA targets and turning struct scatterlist
into a linked list, discussed here:

	http://marc.theaimsgroup.com/?t=102487685000002&r=1&w=2

	I have not started coding this yet because:

	1. I'm tracking down a bug in the next revision of my proposed
	   bio_append patch (which eliminates {read,write}_full_page from
	   fs/buffers.c), and I want to hit that ball out of my court first.

	2. I want to look at aio to see if it has a better way or if it
	   could benefit from this.

	3. I want to accomodate Dave Miller's request for a non-PCI
	   generalization of pci_alloc_consistent, pci_map_single, etc.,
	   first, and that will depend on struct device, for which there are
	   some relevant changes working their way from Patrick Mochel
	   to Linus.

	4. After getting a general dma_alloc_consistent, etc. interface,
	   then I want to create a struct dma_target, to abstract
	   out the DMA capabilities currently maintained by the block
	   layer.  I hope that by doing this in stages, that it will be
	   more palatable to Jens, who expressed concern that the
	   my proposal to go to a linked list for struct scatterlist
	   was a bit too much change.

	Then, I think we'll be in a better position to go to a struct
scatterlist linked list or something similar that can be used by most
if not all big producers of IO.

	In the meantime, killing off kiobufs should be helpful.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-07-11  6:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11  6:09 Adam J. Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09  3:57 Douglas Gilbert
2002-07-09  4:26 ` Andrew Morton
2002-07-09  8:16   ` Ingo Oeser
2002-07-11 17:28   ` Ingo Oeser
2002-07-11 20:43   ` Daniel Phillips
     [not found] <3D2904C5.53E38ED4@zip.com.au.suse.lists.linux.kernel>
2002-07-08  7:26 ` Andi Kleen
2002-07-08  9:19   ` Suparna Bhattacharya
2002-07-08 15:03   ` Matt D. Robinson
2002-07-08  3:19 Andrew Morton
2002-07-08  3:30 ` Lincoln Dale
2002-07-08  7:44 ` Ingo Oeser
2002-07-11  2:25 ` Lincoln Dale
2002-07-11  3:24   ` Andrew Morton
2002-07-11  3:25     ` Lincoln Dale
2002-07-11 19:52   ` Jesse Barnes
2002-07-11 23:40     ` Lincoln Dale

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=200207110609.XAA20931@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=dougg@torque.net \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    /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®