All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Jens Axboe <axboe@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: IOMMU and scatterlist limits
Date: Thu, 17 Nov 2005 10:49:43 +0100	[thread overview]
Message-ID: <437C5237.3080008@drzeus.cx> (raw)
In-Reply-To: <20051117093848.GA7787@suse.de>

Jens Axboe wrote:
> On Thu, Nov 17 2005, Pierre Ossman wrote:
>   
>> Ok. Being a block device, the segments are usually rather large so the
>> overhead of setting up many DMA transfers shouldn't be that terrible.
>>     
>
> The segments will typically be paged size, so could be worse. It all
> depends on what your command overhead is like whether it hurts
> performance a lot or not.
>
>   

MMC overhead is a lot larger than sending new addr/len tuples to the 
hardware. So I suppose there is performance to be gained by iterating 
over the segments inside the driver.

Thanks for clearing things up. Maybe someone could update 
DMA-mapping.txt with the things you've explained to me here *hint* ;)

Rgds
Pierre


  reply	other threads:[~2005-11-17  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  8:34 IOMMU and scatterlist limits Pierre Ossman
2005-11-17  8:54 ` Jens Axboe
2005-11-17  9:02   ` Pierre Ossman
2005-11-17  9:13     ` Jens Axboe
2005-11-17  9:27       ` Pierre Ossman
2005-11-17  9:38         ` Jens Axboe
2005-11-17  9:49           ` Pierre Ossman [this message]
2005-11-17 12:02             ` Jens Axboe
2005-12-18 22:41           ` Pierre Ossman
2005-12-20 11:10             ` Tejun Heo
2005-12-20 11:36               ` Pierre Ossman
2005-12-20 12:04                 ` Tejun Heo
2005-12-20 12:28                   ` Pierre Ossman

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=437C5237.3080008@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=axboe@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.