xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: annie li <annie.li@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: david.vrabel@citrix.com, ian.campbell@citrix.com,
	konrad.wilk@oracle.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/3 V2] xen-netback: switch to NAPI + kthread 1:1 model
Date: Tue, 28 May 2013 22:35:43 +0800	[thread overview]
Message-ID: <51A4C0BF.7060504@oracle.com> (raw)
In-Reply-To: <1369654183-10536-1-git-send-email-wei.liu2@citrix.com>


On 2013-5-27 19:29, Wei Liu wrote:
> * This is a xen-devel only post, since we have not reached concesus on
>    what to add / remove in this new model. This series tries to be
>    conservative about adding in new feature compared to V1.
>
> This series implements NAPI + kthread 1:1 model for Xen netback.
>
> This model
>   - provides better scheduling fairness among vifs
>   - is prerequisite for implementing multiqueue for Xen network driver
>
> The first two patches are ground work for the third patch. First one
> simplifies code in netback, second one can reduce memory footprint if we
> switch to 1:1 model.
>
> The third patch has the real meat:
>   - make use of NAPI to mitigate interrupt
>   - kthreads are not bound to CPUs any more, so that we can take
>     advantage of backend scheduler and trust it to do the right thing
>
> Change since V1:
>   - No page pool in this version. Instead page tracking facility is
>     removed.

What is your thought about page pool in V1? will you re-post it later on?

Thanks
Annie
>
> Wei Liu (3):
>    xen-netback: remove page tracking facility
>    xen-netback: switch to per-cpu scratch space
>    xen-netback: switch to NAPI + kthread 1:1 model
>
>   drivers/net/xen-netback/common.h    |   92 ++--
>   drivers/net/xen-netback/interface.c |  122 +++--
>   drivers/net/xen-netback/netback.c   |  959 +++++++++++++++--------------------
>   3 files changed, 537 insertions(+), 636 deletions(-)
>

  parent reply	other threads:[~2013-05-28 14:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 11:29 [PATCH 0/3 V2] xen-netback: switch to NAPI + kthread 1:1 model Wei Liu
2013-05-27 11:29 ` [PATCH 1/3] xen-netback: remove page tracking facility Wei Liu
2013-05-28  9:21   ` David Vrabel
2013-05-29  1:43     ` Matt Wilson
2013-05-29  8:12       ` Wei Liu
2013-05-27 11:29 ` [PATCH 2/3] xen-netback: switch to per-cpu scratch space Wei Liu
2013-05-28  9:47   ` annie li
2013-05-28 10:17     ` Wei Liu
2013-05-28 13:18   ` Konrad Rzeszutek Wilk
2013-05-28 13:36     ` David Vrabel
2013-05-28 13:54       ` Wei Liu
2013-05-27 11:29 ` [PATCH 3/3] xen-netback: switch to NAPI + kthread 1:1 model Wei Liu
2013-05-28 13:37   ` David Vrabel
2013-05-28 13:40     ` Wei Liu
2013-05-28 14:35 ` annie li [this message]
2013-05-28 15:09   ` [PATCH 0/3 V2] " Wei Liu
2013-06-11 10:06 ` David Vrabel
2013-06-11 10:15   ` Wei Liu
2013-06-12 13:44     ` Andrew Bennieston
2013-06-13  9:01       ` Wei Liu
2013-06-13 11:18         ` Andrew Bennieston
2013-06-13 13:06           ` Wei Liu
2013-07-03 12:45     ` Andrew Bennieston
2013-07-03 16:07       ` Wei Liu

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=51A4C0BF.7060504@oracle.com \
    --to=annie.li@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).