From: Jens Axboe <axboe@suse.de>
To: "Gérard Roudier" <groudier@free.fr>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: SYM-2 patches against latest kernels available
Date: Mon, 5 Nov 2001 08:21:50 +0100 [thread overview]
Message-ID: <20011105082150.H2580@suse.de> (raw)
In-Reply-To: <20011104195145.J10022@suse.de> <20011104174948.I2222-100000@gerard>
In-Reply-To: <20011104174948.I2222-100000@gerard>
On Sun, Nov 04 2001, G?rard Roudier wrote:
> > > Didn't see any. Only the dma_addr_t thing can be 32 bit or 64 bit
> > > depending on some magic. Apart this, the driver is asking for the
> > > appropriate dma mask given the configured dma adressing mode.
> >
> > I've looked over the sym-2 and it is using pci_map_sg so it's 64-bit
> > safe for sg transfers at least. For non-sg requests you are using
> > pci_map_single, but you can't do any better because the mid layer is
> > handing you virtual addresses in request_buffer currently anyways...
>
> If there is some platform-specific thing that allows to handle map_single
> more right:), I can go with it. Would be fine to get IA64 and Alpha
> actually PCI-64 bit safe even by using some software shoehorn for that. :)
IA64 and Alpha is fine, the problem with the non-sg request is just
32-bit archs with highmem support. For that we need to pass in
page/offset values instead of a virtual address.
> > > PS: There is some pci64* API on some arch., but nobody will want to
> > > ever use it, in my opinion.
> >
> > You are doing it right :-)
>
> You mean as right as possible? :)
Indeed :-)
--
Jens Axboe
next prev parent reply other threads:[~2001-11-05 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 13:04 Gérard Roudier
2001-11-04 15:54 ` Jeff Garzik
2001-11-04 15:12 ` Gérard Roudier
2001-11-04 18:51 ` Jens Axboe
2001-11-04 16:56 ` Gérard Roudier
2001-11-05 7:21 ` Jens Axboe [this message]
2001-11-05 18:48 ` Gérard Roudier
2001-11-04 15:49 ` Gérard Roudier
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=20011105082150.H2580@suse.de \
--to=axboe@suse.de \
--cc=groudier@free.fr \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®