xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: openlui <openlui@126.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Question about seperating request and response ring in PV network
Date: Fri, 10 Jul 2015 09:41:10 +0800 (CST)	[thread overview]
Message-ID: <5d0bc7e7.177a0.14e759f98cd.Coremail.openlui@126.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]

Hi, all:
    I am trying to improve the performance of netfront/netback, and  I found that there were some discussion about PV network performance improvement in devel mailing list ([1]). The proposals mentioned  in [1] are helpful, such as multipage ring,  multiqueue, etc, and some of them have already merged into upstream.
    However, I am wondering if we have already used multipage ring,  why "seperate request and response ring" listed in [1] is also helpful for performance improvement? I have read the implementation of vmxnet3 driver, it does have separated request and response rings, but I can not understand what the advantage of this method is.
    Thanks.

[1] http://lists.xen.org/archives/html/xen-devel/2013-05/msg01904.html
----
Best Regards
Lui



[-- Attachment #1.2: Type: text/html, Size: 1197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2015-07-10  1:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10  1:41 openlui [this message]
2015-07-10  8:09 ` Question about seperating request and response ring in PV network 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=5d0bc7e7.177a0.14e759f98cd.Coremail.openlui@126.com \
    --to=openlui@126.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).