From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Eliezer Tamir <eliezer.tamir@linux.intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xen.org, Eric Dumazet <edumazet@google.com>,
Li Zefan <lizefan@huawei.com>,
david.vrabel@citrix.com, Zoltan Kiss <zoltan.kiss@citrix.com>,
malcolm.crossley@citrix.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Xen-devel] [PATCH] net/core: Order-3 frag allocator causes SWIOTLB bouncing under Xen
Date: Thu, 5 Sep 2013 08:39:06 +0100 [thread overview]
Message-ID: <1378366746.6935.35.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20130904211110.GA17758@phenom.dumpdata.com>
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.
next prev parent reply other threads:[~2013-09-05 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 20:47 Zoltan Kiss
2013-09-04 21:00 ` Eric Dumazet
2013-09-04 21:11 ` Konrad Rzeszutek Wilk
2013-09-05 7:39 ` Ian Campbell [this message]
2013-09-06 13:27 ` [Xen-devel] " Konrad Rzeszutek Wilk
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378366746.6935.35.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=edumazet@google.com \
--cc=eliezer.tamir@linux.intel.com \
--cc=eric.dumazet@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=malcolm.crossley@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@citrix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome