Re: Memory BARs for sfc devices unmapped in 3.0-rc1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 03, 2011 at 02:16:14PM -0700, Yinghai Lu wrote:
> On 06/03/2011 01:22 PM, Ram Pai wrote:
> >>>
> >>> Ram, can you check those two patches to see if it has any problem with your setup?
> >>
> >> No. the patch fails on my platform to enable SRIOV. The SRIOV BARs fail to allocate. debugging..
> > 
> > It fails to adjust-in a large window size, 4 times more than the one already assigned, to the bridge
> > below which the SRIOV device resides.
> > 
> > Adjusting in a smaller window size, like that for hotplug, more than often succeed.
> > But adjusting in  manytimes larger size cannot be guaranteed to work.
> 
> wonder if hotplug bridge nice-to-have get allocated before SRIOV cause failure in your system.

No. The SRIOV device is not on a hotplug bridge.

adjust_resource() is failing because it is unable to extend the resource size
in-place, since the adjacent space is already allocated. The only way to
satisfy this to relocate the resource to a large enough free chunk.  looks like
adjust_resource() is not the right interface for our need.  We need some kind
of new interface that relocates the resource to a large enough location within
the parent's resource range.

RP
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux