[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110706104848.7e9d21fc@jbarnes-desktop>
Date: Wed, 6 Jul 2011 10:48:48 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Oliver Hartkopp <socketcan@...tkopp.net>
Cc: Ram Pai <linuxram@...ibm.com>, torvalds@...ux-foundation.org,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
yinghai@...nel.org, bhutchings@...arflare.com, bhelgaas@...gle.com,
linux@...inikbrodowski.net
Subject: Re: [PATCH 3/5 v2] PCI: make SRIOV resources optional
On Fri, 01 Jul 2011 08:01:33 +0200
Oliver Hartkopp <socketcan@...tkopp.net> wrote:
> On 01.07.2011 01:47, Ram Pai wrote:
> > From: Yinghai Lu <yinghai@...nel.org>
> >
> > From: Yinghai Lu <yinghai@...nel.org>
> >
> > Allocate resources to SRIOV BARs only after all other required
> > resource-requests are satisfied. Dont retry if resource allocation for SRIOV
> > BARs fail.
> >
> > Signed-off-by: Ram Pai <linuxram@...ibm.com>
> > Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>
> Tested-by: Oliver Hartkopp <socketcan@...tkopp.net>
>
> I applied the whole patchset and it looks very similar to the dmsg output
> before the problematic commit that caused the regression.
Ok Oliver, can I ask you to test one more tree? We'll shoot for
including Ram's patches in -next, but I've just included his other
patch to disable the new realloc code by default for the current
kernel. Can you give my for-linus tree a try and make sure it gives
you back the old behavior? Thanks a lot for your diligent testing so
far.
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 is the
tree, then check out the "for-linus" branch.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists