From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
Ian Pratt <Ian.Pratt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [Pv-ops][PATCH] Netback multiple tasklet support
Date: Wed, 09 Dec 2009 12:23:03 -0800 [thread overview]
Message-ID: <4B200727.8040000@goop.org> (raw)
In-Reply-To: <EADF0A36011179459010BDF5142A457501D13FDE62@pdsmsx502.ccr.corp.intel.com>
On 12/08/09 01:22, Xu, Dongxiao wrote:
> Jeremy,
> I have revised the patch according to your suggestion. See attachment.
> 0001: Keep group number as 1, and put all the global/static variables to struct xen_netbk. Do some preparations for multiple tasklets support.
> 0002: Support for netback multiple tasklet.
> 0003: Use kernel thread to replace the tasklet in order to ensure the dom0 userspace QoS.
>
Thanks, this looks much better. The only thing which lept out at me
from a first reading is that "group_nr" is still too generic a name for
a global symbol. Something like "xen_netbk_nr_groups" perhaps?
Also, is it worth making it a tunable? Presumably it needn't scale
exactly with the number of dom0 cpus; if you only have one or two gbit
interfaces, then you could saturate that pretty quickly with a small
number of cpus, regardless of how many domains you have.
I've pushed this out in its own branch:
xen/dom0/backend/netback-tasklet; please post any future patches against
this branch.
J
next prev parent reply other threads:[~2009-12-09 20:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 2:26 [Pv-ops][PATCH] Netback multiple tasklet support Xu, Dongxiao
2009-11-27 9:42 ` Ian Campbell
2009-11-27 16:08 ` Xu, Dongxiao
2009-11-27 16:15 ` Ian Pratt
2009-11-27 16:57 ` Xu, Dongxiao
2009-11-28 13:15 ` Ian Pratt
2009-12-02 10:17 ` Xu, Dongxiao
2009-12-03 21:28 ` Jeremy Fitzhardinge
2009-12-04 2:13 ` Xu, Dongxiao
2009-12-04 2:33 ` Jeremy Fitzhardinge
2009-12-08 9:22 ` Xu, Dongxiao
2009-12-09 20:23 ` Jeremy Fitzhardinge [this message]
2009-12-10 3:29 ` Xu, Dongxiao
2009-12-10 18:01 ` Jeremy Fitzhardinge
2009-12-11 1:34 ` Xu, Dongxiao
2010-04-26 14:27 ` [Pv-ops][PATCH 0/3] Resend: Netback multiple thread support Xu, Dongxiao
2010-04-27 0:19 ` Konrad Rzeszutek Wilk
2010-04-27 0:40 ` Xu, Dongxiao
2010-04-27 3:02 ` Xu, Dongxiao
2010-04-27 10:49 ` Steven Smith
2010-04-27 18:37 ` Jeremy Fitzhardinge
2010-04-28 9:31 ` Steven Smith
2010-04-28 11:36 ` Xu, Dongxiao
2010-04-28 12:04 ` Steven Smith
2010-04-28 13:33 ` Xu, Dongxiao
2010-04-30 7:35 ` Steven Smith
2010-04-28 10:27 ` Xu, Dongxiao
2010-04-28 11:51 ` Steven Smith
2010-04-28 12:23 ` Xu, Dongxiao
2010-04-28 12:43 ` Jan Beulich
2010-04-30 7:29 ` Steven Smith
2010-04-30 8:27 ` Jan Beulich
2009-12-10 9:07 ` [Pv-ops][PATCH] Netback multiple tasklet support Ian Campbell
2009-12-10 17:54 ` Jeremy Fitzhardinge
2009-12-10 18:07 ` Ian Campbell
2009-12-11 8:34 ` Jan Beulich
2009-12-11 9:34 ` Ian Campbell
2009-12-11 14:24 ` Konrad Rzeszutek Wilk
2010-03-17 8:46 ` [PATCH] [pv-ops] fix dom0 S3 when MSI is used Cui, Dexuan
2010-03-17 14:28 ` Konrad Rzeszutek Wilk
2010-03-18 3:05 ` Cui, Dexuan
2010-03-19 1:04 ` Jeremy Fitzhardinge
2010-03-19 1:03 ` Jeremy Fitzhardinge
2010-03-19 1:29 ` Cui, Dexuan
2010-01-13 10:17 ` [Pv-ops][PATCH] Netback multiple tasklet support Jan Beulich
2010-01-14 16:55 ` 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=4B200727.8040000@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Steven.Smith@eu.citrix.com \
--cc=dongxiao.xu@intel.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.