From: Grant Grundler <grundler@parisc-linux.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: Matthew Wilcox <matthew@wil.cx>, Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
grundler@parisc-linux.org, mingo@elte.hu, tglx@linutronix.de,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci: print out DMA mask info
Date: Sun, 12 Oct 2008 01:38:59 -0600 [thread overview]
Message-ID: <20081012073859.GE20056@colo.lackof.org> (raw)
In-Reply-To: <ada1vyojrme.fsf@cisco.com>
On Fri, Oct 10, 2008 at 10:18:33AM -0700, Roland Dreier wrote:
> > Open-coding DMA_BIT_MASK() within your driver means that we no longer
> > have a canonical list of DMA masks in one place. Instead we have to
> > grep the entire tree and come up with more-or-less complex scripts to
> > figure out which bit masks are actually in use.
>
> Out of curiousity, why do we care about that list?
Originally, I used to track down IO perf issues when porting drivers to ia64.
But knowing the dma masks in use on specific platforms might allow
folks to disable DMA_ZONE (like ia64 since it's always guarateed
either a SWIOTLB or real IOMMU).
Any other uses?
thanks,
grant
>
> - R.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-12 7:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 23:02 Yinghai Lu
2008-10-09 21:18 ` Grant Grundler
2008-10-09 21:27 ` Yinghai Lu
2008-10-09 21:35 ` Matthew Wilcox
2008-10-09 21:51 ` Yinghai Lu
2008-10-09 22:55 ` Grant Grundler
2008-10-09 23:05 ` Yinghai Lu
2008-10-10 2:40 ` FUJITA Tomonori
2008-10-10 4:56 ` Yinghai Lu
2008-10-10 6:08 ` FUJITA Tomonori
2008-10-10 6:32 ` Yinghai Lu
2008-10-10 7:32 ` FUJITA Tomonori
2008-10-12 7:16 ` Grant Grundler
2008-10-10 22:45 ` Grant Grundler
2008-10-14 6:50 ` FUJITA Tomonori
2008-10-12 7:11 ` Grant Grundler
2008-10-23 1:45 ` [PATCH] pci: show dma_mask bits in /sys Yinghai Lu
2008-10-23 3:28 ` Matthew Wilcox
2008-10-23 4:19 ` Yinghai Lu
2008-10-23 6:44 ` Grant Grundler
2008-10-23 8:38 ` Rolf Eike Beer
2008-10-23 15:39 ` Greg KH
2008-10-23 18:37 ` H. Peter Anvin
2008-10-23 19:36 ` Grant Grundler
2008-10-23 19:49 ` Greg KH
2008-10-24 10:50 ` Andi Kleen
2008-11-01 17:10 ` Grant Grundler
2008-10-23 6:48 ` Grant Grundler
2008-10-23 6:51 ` Yinghai Lu
2008-10-23 19:28 ` Grant Grundler
2008-10-10 2:40 ` [PATCH] pci: print out DMA mask info FUJITA Tomonori
2008-10-10 2:59 ` FUJITA Tomonori
2008-10-10 2:40 ` FUJITA Tomonori
2008-10-10 15:48 ` Jesse Barnes
2008-10-10 16:19 ` Yinghai Lu
2008-10-10 16:28 ` Jesse Barnes
2008-10-10 16:33 ` Matthew Wilcox
2008-10-10 16:46 ` Yinghai Lu
2008-10-10 17:12 ` Matthew Wilcox
2008-10-10 17:18 ` Roland Dreier
2008-10-12 7:38 ` Grant Grundler [this message]
2008-10-12 7:20 ` 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=20081012073859.GE20056@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=rdreier@cisco.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome