linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gérard Roudier" <groudier@free.fr>
To: "David S. Miller" <davem@redhat.com>
Cc: <axboe@suse.de>, <linux-kernel@vger.kernel.org>, <andrea@suse.de>
Subject: Re: [patch] zero-bounce highmem I/O
Date: Wed, 15 Aug 2001 21:20:17 +0200 (CEST)	[thread overview]
Message-ID: <20010815205954.A1159-100000@gerard> (raw)
In-Reply-To: <20010815.032218.55508716.davem@redhat.com>



On Wed, 15 Aug 2001, David S. Miller wrote:

>    From: Jens Axboe <axboe@suse.de>
>    Date: Wed, 15 Aug 2001 11:26:21 +0200
>
>    Ok, here's an updated version. Maybe modulo the struct scatterlist
>    changes, I'd like to see this included in 2.4.x soonish. Or at least the
>    interface we agree on -- it'll make my life easier at least. And finally
>    provide driver authors with something not quite as stupid as struct
>    scatterlist.
>
> Jens, have a look at the patch I have below.  What do you
> think about it?  Specifically the set of interfaces.
>
> Andrea, I am very much interested in your input as well.

Here is some input you donnot seem interested in. Too bad for you! :-)

Some drivers may want to allocate internal DMAable data structures in a 32
bit DMAable address range but also may want to support 64 bit DMA
addressing for user data. This applies to the sym53c8xx driver (which is
not quite ready for 64 bit DMA adressing for now) and to the aic7xxx
driver which seems to be ready. The reason is for simplicity and may-be
feasibility and given that driver internal data structures donnot require
that much memory, this should not make memory pressure at all on the 32
bit DMAable range.

The current solution consists in tampering the dma_mask in the pci_dev
structure prior to allocating DMAable memory. Not really clean...
Some interface that would allow to provide some masks as argument would be
cleaner, in my opinion. Btw, the pci_set_* interface does not seem cleaner
to me than hacking the corresponding field in the pcidev structure directly.


> I would like to kill two birds with one stone here if
> we can.   The x86 versions of the asm/pci.h and
> asm/scatterlist.h bits are pretty mindless and left as
> an exercise to the reader :-)

[... b****ed patch removed since reader should already have it :) ...]

Later,
  Gérard.


  parent reply	other threads:[~2001-08-15 19:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15  7:50 [patch] zero-bounce highmem I/O Jens Axboe
2001-08-15  9:11 ` David S. Miller
2001-08-15  9:17   ` Jens Axboe
2001-08-15  9:26   ` Jens Axboe
2001-08-15 10:22   ` David S. Miller
2001-08-15 11:13     ` Jens Axboe
2001-08-15 11:47     ` David S. Miller
2001-08-15 12:07       ` Jens Axboe
2001-08-15 12:35       ` David S. Miller
2001-08-15 13:10         ` Jens Axboe
2001-08-15 14:25           ` David S. Miller
2001-08-16 11:51             ` Jens Axboe
2001-08-16 11:56             ` David S. Miller
2001-08-16 12:03               ` Jens Axboe
2001-08-16 12:14               ` Gerd Knorr
2001-08-16 12:27               ` David S. Miller
2001-08-16 12:48                 ` Jens Axboe
2001-08-16 12:56                 ` Jens Axboe
2001-08-16 13:08                 ` David S. Miller
2001-08-16 12:34               ` David S. Miller
2001-08-16 13:35                 ` Gerd Knorr
2001-08-16 14:15                 ` David S. Miller
2001-08-16 12:28             ` kill alt_address (Re: [patch] zero-bounce highmem I/O) David S. Miller
2001-08-15 14:02         ` [patch] zero-bounce highmem I/O David S. Miller
2001-08-16  5:52           ` Jens Axboe
2001-08-15 19:20     ` Gérard Roudier [this message]
2001-08-16  8:12     ` David S. Miller
     [not found] <no.id>
2001-08-16 14:56 ` Alan Cox
2001-08-17 10:18   ` Gerd Knorr

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=20010815205954.A1159-100000@gerard \
    --to=groudier@free.fr \
    --cc=andrea@suse.de \
    --cc=axboe@suse.de \
    --cc=davem@redhat.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;
as well as URLs for NNTP newsgroup(s).