From: tangming <tangming__06@163.com>
To: xen-devel@lists.xensource.com
Subject: Xen network performance issue
Date: Sun, 30 May 2010 02:51:02 +0800 (CST) [thread overview]
Message-ID: <1da0b95.5939.128e56728a1.Coremail.tangming__06@163.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]
Hi, Guys
I was obsessed by the following issue for weeks :-), and could you please help me get rid of it? Many thanks!!!
Recentlly I used the standard Suse10sp2 as HVM guest(domU), and installed the para-virtualization network card driver(xen-vnif.ko) within it. But when I test the performance on domU by continuously sending/receiving large amount of packages I found that the writing(sending) speed can up to 100MB/s, while the reading(receiving) speed only 50MB/s, not sure why.
I know that the para-virtualization network driver used two I/O ring buffers, one for transmitting and the other for receiving, and I think the rx_buffer may be the issue, but not sure.
Two more questions:
1. Does the front_end driver use polling or event notification for discovering the data arrival?
2. Does the back_end driver use transferring or copying for putting the data to the grant pages of front_end?
Do you guys think the above methods used by the network driver is the root cause? And how can we decide to use which method (polling vs. notification, transferring vs. copying) in the specified situation for high throughput?
Could you please give me some suggestions for locating this issue and resolving it? Thanks in advance!!!
[-- Attachment #1.2: Type: text/html, Size: 1751 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2010-05-29 18:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1da0b95.5939.128e56728a1.Coremail.tangming__06@163.com \
--to=tangming__06@163.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 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).