From: Christoph Hellwig <hch@infradead.org>
To: Jes Sorensen <jes@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, Mark Maule <maule@sgi.com>,
akpm@osdl.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] altix: export sn_pcidev_info_get
Date: Sat, 25 Feb 2006 11:55:12 +0000 [thread overview]
Message-ID: <20060225115512.GA24439@infradead.org> (raw)
In-Reply-To: <yq0r75x6jmn.fsf@jaguar.mkp.net>
On Tue, Feb 21, 2006 at 06:23:12AM -0500, Jes Sorensen wrote:
> Point is that there are cases where tuning requires you to know what
> PCI bridge is below you in order to get the best performance out of a
> card. One can keep a PCI ID blacklist to handle tuning of the PCI
> bridge itself, but it can't handle things that needs to be tuned
> by setting the PCI device's own registers.
>
> Having a generic API to export this information would be a good thing
> IMHO.
So please submit a patch to add querying/tuning pci bridges. And please
make it _GPL exports so people don't accidentally use it in their illegal
drivers.
next prev parent reply other threads:[~2006-02-25 11:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 16:23 [PATCH] altix: export sn_pcidev_info_get Mark Maule
2006-02-20 20:17 ` Christoph Hellwig
2006-02-20 21:39 ` Andrew Morton
2006-02-20 21:39 ` Andrew Morton
2006-02-21 10:48 ` Christoph Hellwig
2006-02-25 11:55 ` Christoph Hellwig
2006-02-21 2:47 ` Mark Maule
2006-02-21 2:47 ` Mark Maule
2006-02-21 8:03 ` Arjan van de Ven
2006-02-21 8:03 ` Arjan van de Ven
2006-02-21 8:20 ` Christian Hildner
2006-02-21 8:20 ` Christian Hildner
2006-02-21 10:36 ` Christoph Hellwig
2006-02-21 11:23 ` Jes Sorensen
2006-02-21 11:23 ` Jes Sorensen
2006-02-25 11:55 ` Christoph Hellwig [this message]
2006-03-01 13:34 ` Jes Sorensen
2006-03-01 13:34 ` Jes Sorensen
2006-03-01 14:41 ` Luck, Tony
2006-03-01 14:41 ` Luck, Tony
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=20060225115512.GA24439@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maule@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.