From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [RFC PATCH V2] New Xen netback implementation
Date: Sun, 29 Jan 2012 16:37:46 -0500 [thread overview]
Message-ID: <20120129213746.GA7164@phenom.dumpdata.com> (raw)
In-Reply-To: <1327844561.2911.5.camel@leeds.uk.xensource.com>
On Sun, Jan 29, 2012 at 01:42:41PM +0000, Wei Liu wrote:
> On Fri, 2012-01-27 at 19:22 +0000, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jan 17, 2012 at 01:46:56PM +0000, Wei Liu wrote:
> > > A new netback implementation which includes three major features:
> > >
> > > - Global page pool support
> > > - NAPI + kthread 1:1 model
> > > - Netback internal name changes
> > >
> > > Changes in V2:
> > > - Fix minor bugs in V1
> > > - Embed pending_tx_info into page pool
> > > - Per-cpu scratch space
> > > - Notification code path clean up
> > >
> > > This patch series is the foundation of furture work. So it is better
> > > to get it right first. Patch 1 and 3 have the real meat.
> >
> > I've been playing with these patches and couple of things
> > came to my mind:
> > - would it make sense to also register to the shrinker API? This way
> > if the host is running low on memory it can squeeze it out of the
> > pool code. Perhaps a future TODO..
> > - I like the pool code. I was thinking that perhaps (in the future)
> > it could be used by blkback as well, as it runs into "not enought
> > request structure" with the default setting. And making this dynamic
> > would be pretty sweet.
>
> Interesting thoughts worth adding to TODO list. But I'm focusing on
> multi-page ring support and split event channel at the moment, which
> should help improve performance on 10G network. Hopefully I can submit
> RFC patch V3 in a few days. ;-)
>
> > - This patch set solves the CPU banding problem I've seen with the
> > older netback. The older one I could see X netback threads eating 80%
> > of CPU. With this one, the number is down to 13-14%.
> >
> > So you can definitly stick 'Tested-by: Konrad.." on them. And definitly
> > Reviewed-by on the first two - hadn't had a chance to look at the rest.
> >
>
> Thanks for your extensive test and review.
Sure. I also did some testing with limiting the amount of CPUs and found
that 'xl vcpu-set 0 N' make netback not work anymore :-(
>
>
> Wei.
next prev parent reply other threads:[~2012-01-30 14:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 13:46 [RFC PATCH V2] New Xen netback implementation Wei Liu
2012-01-17 13:46 ` [RFC PATCH V2 1/8] netback: page pool version 1 Wei Liu
2012-01-17 13:46 ` [RFC PATCH V2 2/8] netback: add module unload function Wei Liu
2012-01-17 13:46 ` [RFC PATCH V2 3/8] netback: switch to NAPI + kthread model Wei Liu
2012-01-17 17:07 ` Stephen Hemminger
2012-01-17 17:11 ` Wei Liu
2012-01-17 17:11 ` Wei Liu
2012-01-17 13:47 ` [RFC PATCH V2 4/8] netback: switch to per-cpu scratch space Wei Liu
2012-01-17 13:47 ` [RFC PATCH V2 5/8] netback: add module get/put operations along with vif connect/disconnect Wei Liu
2012-01-17 13:47 ` [RFC PATCH V2 6/8] netback: melt xen_netbk into xenvif Wei Liu
2012-01-17 13:47 ` [RFC PATCH V2 7/8] netback: alter internal function/structure names Wei Liu
2012-01-17 13:47 ` [RFC PATCH V2 8/8] netback: remove unwanted notification generation during NAPI processing Wei Liu
2012-01-27 19:22 ` [RFC PATCH V2] New Xen netback implementation Konrad Rzeszutek Wilk
2012-01-29 13:42 ` Wei Liu
2012-01-29 13:42 ` Wei Liu
2012-01-29 21:37 ` Konrad Rzeszutek Wilk [this message]
2012-01-30 15:01 ` Wei Liu
2012-01-30 15:01 ` Wei Liu
2012-01-30 18:27 ` Wei Liu
2012-01-30 18:27 ` Wei Liu
2012-01-30 18:30 ` Wei Liu
2012-01-30 18:30 ` Wei Liu
2012-01-30 19:41 ` Wei Liu
2012-01-30 19:41 ` Wei Liu
2012-01-30 15:07 ` Ian Campbell
2012-01-30 15:21 ` Konrad Rzeszutek Wilk
2012-01-30 15:49 ` Ian Campbell
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=20120129213746.GA7164@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.