On Sun, Jan 15, 2012 at 08:54:46PM -0800, Yinghai Lu wrote: > On Sun, Jan 15, 2012 at 7:26 PM, Ram Pai <linuxram@xxxxxxxxxx> wrote: > >> Also I updated for-pci2 in my tree. > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git > >> for-pci2 > >> > >> Peter Henriksson, > >> Can you try for-pci2 branch on your setup with Xonar DX? > > > > Peter should confirm it. But this patch will not fix the issue AFAICT. > > Do you have similar setup to test that ? No. :( > > > Its not just about 'not enough resources', it also about making the right > > choice of 'who should get the resource if there is contention'. Only the BIOS > > knows about it. But we trash the BIOS's allocation and don't use that > > knowledge when it comes to making those hard choices. > > in extreme case, will let the user to use "pci=norealloc" to disable > changing pci bridge resource set by BIOS. I know its a pathological case. But still this issue will be viewed as a regression. I had to struggle to solve this regression in order to get your realloc patch re-accepted. Don't know if you can successfully make a case to by-pass the regression this time. One way to solve this problem is to allocate 'required' resources first, and later aggressively try to allocate 'required+optional' resources. However aggressively allocation of those 'required+optional' resource would require ensuring minimal internal fragmentation. 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
