LKML Archive on
help / color / mirror / Atom feed
From: Greg KH <>
To: Daniel Yeisley <>
Subject: Re: [PATCH] I/O space boot parameter
Date: Tue, 20 Mar 2007 13:26:52 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1174411538.23830.28.camel@localhost.localdomain>

On Tue, Mar 20, 2007 at 01:25:38PM -0400, Daniel Yeisley wrote:
> On Tue, 2007-03-20 at 11:00 -0700, Greg KH wrote:
> > On Tue, Mar 20, 2007 at 12:18:24PM -0400, Daniel Yeisley wrote:
> > > It has been mentioned before that large systems with a lot of PCI buses
> > > have issues with the 64k I/O space limit.  The ES7000 has a BIOS option
> > > to either assign I/O space to all adapters, or only to those that need
> > > it.  A list of supported adapters that don't need it is kept in the
> > > BIOS.  When this option is used, the kernel sees the BARs on the
> > > adapters and still tries to assign I/O space (until it runs out).  I've
> > > written a patch to implement a boot parameter that tells the kernel not
> > > to assign I/O space if the BIOS hasn't.  
> > 
> > How prelevant are machines like this?  And why are the BARs on these
> > devices wrong?
> > 
> I don't have any sales numbers, but I can tell you that our current
> systems can have up to 64 PCI buses.  
> I've been working with Emulex cards, and my understanding is that the
> BARs on the devices aren't wrong, but we can't allocate 4k of I/O space
> for each one.  So we maintain a list in the BIOS of devices that don't
> actually need I/O space and then don't assign it.  I've tested an a
> x86_64 system with 20+ adapters and saw all the disks attached without
> any problems.

Ah.  Others are working on providing a fix for this too, but it is being
done in the drivers themselves, not in the pci core.  Look in the
linux-pci mailing list archives for those patches (I don't think they
every went into mainline for some reason, but I might be wrong...)

I suggest you work with those developers, as they have the same issue
that you are trying to solve here.


greg k-h

  reply	other threads:[~2007-03-20 20:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 16:18 Daniel Yeisley
2007-03-20 18:00 ` Greg KH
2007-03-20 17:25   ` Daniel Yeisley
2007-03-20 20:26     ` Greg KH [this message]
2007-03-21 13:37       ` Daniel Yeisley
2007-03-21 23:57         ` Greg KH
2007-03-22 15:08           ` Daniel Yeisley
2007-03-20 20:05   ` Eric W. Biederman
     [not found] <>
     [not found] ` <>
     [not found]   ` <fa.236bWOhrGT0j4UCxsmp32/>
     [not found]     ` <fa.5exuGSZI65YO9pz/5yzd/>
     [not found]       ` <>
2007-03-21 23:21         ` Robert Hancock

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [PATCH] I/O space boot parameter' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).