public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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: 01 Mar 2006 08:34:41 -0500	[thread overview]
Message-ID: <yq0hd6i70ge.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060225115512.GA24439@infradead.org>

>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:

Christoph> On Tue, Feb 21, 2006 at 06:23:12AM -0500, Jes Sorensen
Christoph> 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.

Christoph> So please submit a patch to add querying/tuning pci
Christoph> bridges.  And please make it _GPL exports so people don't
Christoph> accidentally use it in their illegal drivers.

Mark checked with the gfx people and it seems that the requirement for
this information was a leftover from an older codebase and they don't
actually need it anymore. Anyway, I'm not sure what illegal drivers
you keep referring to.

Tony/Andrew, it should be ok to take the export out again.

I'll try to look into doing a more generic interface for querying
information about the low level PCI briges at some point. Since
there's no new users screaming for this right now and most current
drivers that will benefit from it are somewhat old, it's not going to
be my top priority item at this moment. Since this would be an
interface, it would obviously have to a regular symbol export.

Cheers,
Jes

  reply	other threads:[~2006-03-01 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060214162337.GA16954@sgi.com>
2006-02-20 20:17 ` [PATCH] altix: export sn_pcidev_info_get Christoph Hellwig
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  8:03     ` Arjan van de Ven
2006-02-21  8:20       ` Christian Hildner
2006-02-21 10:36     ` Christoph Hellwig
2006-02-21 11:23       ` Jes Sorensen
2006-02-25 11:55         ` Christoph Hellwig
2006-03-01 13:34           ` Jes Sorensen [this message]
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=yq0hd6i70ge.fsf@jaguar.mkp.net \
    --to=jes@sgi.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox