public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William D Waddington <william.waddington@beezmo.com>
To: linux-kernel@vger.kernel.org
Subject: [RFCLUE4] scatterlist changes
Date: Thu, 15 May 2008 09:51:14 -0700	[thread overview]
Message-ID: <482C6A02.2030600@beezmo.com> (raw)

Hi,

I have just tripped over the scatterlist changes in my out-of-tree
drivers.  I'll deal with it.  When the API stabilizes...

It does bring to mind a simple question:  why limit the scatterlist
to a single page, or require a multiple-page list to be dealt with
as individual pages?

Is this just to avoid vmalloc use?  I don't see anything that requires
a scatterlist to be in physically contiguous memory (at a quick glance
anyway) other than perhaps a preference for the initial allocation
mechanism.  (My actual IOPB list for the DMA hardware is a different
matter entirely, but I don't _think_ I'm confusing the two).

Thanks,
Bill
-- 
--------------------------------------------
William D Waddington
Bainbridge Island, WA, USA
william.waddington@beezmo.com
--------------------------------------------
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch

                 reply	other threads:[~2008-05-15 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=482C6A02.2030600@beezmo.com \
    --to=william.waddington@beezmo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox