[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1378366746.6935.35.camel@dagon.hellion.org.uk>
Date: Thu, 5 Sep 2013 08:39:06 +0100
From: Ian Campbell <Ian.Campbell@...rix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC: Eric Dumazet <eric.dumazet@...il.com>,
Eliezer Tamir <eliezer.tamir@...ux.intel.com>,
Neil Horman <nhorman@...driver.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xen.org,
Eric Dumazet <edumazet@...gle.com>,
Li Zefan <lizefan@...wei.com>, david.vrabel@...rix.com,
Zoltan Kiss <zoltan.kiss@...rix.com>,
malcolm.crossley@...rix.com,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [Xen-devel] [PATCH] net/core: Order-3 frag allocator causes
SWIOTLB bouncing under Xen
On Wed, 2013-09-04 at 17:11 -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Sep 04, 2013 at 02:00:40PM -0700, Eric Dumazet wrote:
> > Maybe you could add proper infrastructure to deal with Xen limitations.
>
> I think Ian posted at some point an sysctl patch for that (more for
> debugging that anything else). And it kind
> of stalled: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01832.html
I think I though you were looking into it from the swiotlb angle?
In any case I don't have time to look into this further.
> Is that what you mean by proper infrastructure ?
>
> Oh wait, did you mean via dev and not the whole system wide sysctl?
The system wide sysctl was not acceptable AFAIR, which seems reasonable.
Per-dev is hard because it affects the native drivers for each physical
NIC when running under Xen, not the Xen PV NIC which we fixed by
splitting compound frags into separate slots on the PV ring.
Ian.
--
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