From: Jes Sorensen <jes@trained-monkey.org>
To: linux-ia64@vger.kernel.org
Subject: [RFC] speeding up pci_unmap_sg() for SAC mappings
Date: Mon, 09 Feb 2004 15:27:39 +0000 [thread overview]
Message-ID: <16423.42731.766788.360790@gargle.gargle.HOWL> (raw)
Hi,
I was looking at the sn2 PCI mapping code and realized how it is costing
to do a basic pci_unmap because the code has to search a table to figure
out which struct dmamap entry matches a given dma address. Clearly the
sn code could be improved in terms of how it is currently implemented,
however there is still the fundamental problem of mapping from a
dma_addr_t to a dma-map entry which I believe all IOMMU code
implmentations suffer from. The pretty way to clean this up would
probably require changing the whole mapping API, however one of the most
interesting cases is pci_unmap_sg.
Christoph suggested that we add an arch dependent pointer to struct
scatterlist that we can use to short circuit the unmap process.
Anyone have any strong objections to this? While it can be considered a
bit hackerish it really should help on performance without making any
visible changes to the end user.
Comments?
Cheers,
Jes
next reply other threads:[~2004-02-09 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 15:27 Jes Sorensen [this message]
2004-02-09 16:38 ` [RFC] speeding up pci_unmap_sg() for SAC mappings Alex Williamson
2004-02-09 16:52 ` Grant Grundler
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=16423.42731.766788.360790@gargle.gargle.HOWL \
--to=jes@trained-monkey.org \
--cc=linux-ia64@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