From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Kaushik Kumar Ram <kaushik@rice.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen dom0 network I/O scalability
Date: Wed, 27 Apr 2011 13:50:25 -0400 [thread overview]
Message-ID: <20110427175025.GD31181@dumpdata.com> (raw)
In-Reply-To: <2D693F50-E757-4DAA-8B67-041CB01AC250@rice.edu>
On Wed, Apr 27, 2011 at 12:30:27PM -0500, Kaushik Kumar Ram wrote:
> Hi folks,
>
> I have a few questions/clarifications about dom0 network I/O scalability. I would appreciate any feedback/pointers.
>
> So the current implementation of netback does not scale beyond a single CPU core, thanks to the use of tasklets, making it a bottleneck (please correct me if I am wrong). I remember coming across some patches which attempts to use softirqs instead of tasklets to solve this issue. But the latest version of linux-2.6-xen.hg repo does not include them. Are they included in some other version of dom0 Linux? Or will they be included in future? This seems like a very important problem to solve especially as the number of VMs and number of CPU cores go up. Is there any fundamental limitation in solving this problem?
You should be using the 2.6.39 kernel or the 2.6.32 to take advantage of those patches.
>
> Thanks.
> --Kaushik
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-27 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 17:30 Xen dom0 network I/O scalability Kaushik Kumar Ram
2011-04-27 17:50 ` Konrad Rzeszutek Wilk [this message]
2011-05-10 2:13 ` Kaushik Kumar Ram
2011-05-10 20:23 ` Konrad Rzeszutek Wilk
2011-05-11 9:31 ` Ian Campbell
2011-05-11 18:43 ` Kaushik Kumar Ram
2011-05-12 8:21 ` Ian Campbell
2011-05-12 20:10 ` Kaushik Kumar Ram
2011-05-13 7:33 ` 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=20110427175025.GD31181@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=kaushik@rice.edu \
--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 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).