From: Pat Gefre <pfg@sgi.com>
To: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@infradead.org
Subject: Re: Altix I/O code reorganization - 7 of 21
Date: Wed, 11 Aug 2004 23:29:25 +0000 [thread overview]
Message-ID: <200408112329.i7BNTP6F163641@fsgi900.americas.sgi.com> (raw)
> 003-pci-support:
> The PCI DMA implementation is still ubercomplicated. See the PCI DMA code
> I sent you long ago.
> Of the code in pci_extensions.c only two are actually used in the kernel
> (snia_pcibr_rrb_alloc and snia_pcidev_endian_set), please remove the unused
> other ones.
>
Yes, the PCI DMA mapping code is very robust and tries to export
the many hardware features that are available on our system. However, not
all of these features are "reachable" via the standard Linux PCI mapping
interfaces. We have removed all unreacheable features. However, we can
still support future requirements with these new interfaces when needed.
Yes, we did look at your patch dated: December 4th 2003. It was very good, but
did not go far enough. We felt that we can trim more of the code. The current
result, we believe is much cleaner and easier to support. The dma path now is
much leaner.
We have removed unused calls in pci_extensions.c. We have also removed the
call snia_pcidev_endian_set. IOC4 endianess is already correctly set by
Prom during configuration and initialization.
For the new code see:
ftp://oss.sgi.com/projects/sn2/sn2-update/003-pci-support
next reply other threads:[~2004-08-11 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 23:29 Pat Gefre [this message]
2004-08-12 9:18 ` Altix I/O code reorganization - 7 of 21 Christoph Hellwig
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=200408112329.i7BNTP6F163641@fsgi900.americas.sgi.com \
--to=pfg@sgi.com \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--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