public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chigurupati, Chaks" <chaks@wichorus.com>
To: Tom Lendacky <tahm@linux.vnet.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Network performance with small packets - continued
Date: Tue, 8 Mar 2011 20:34:44 -0600	[thread overview]
Message-ID: <C99C259E.C1A0%chaks@wichorus.com> (raw)
In-Reply-To: <201103071631.41964.tahm@linux.vnet.ibm.com>

Hi Tom,

My two cents. Please look for [Chaks]

><snip>
>Comparing the transmit path to the receive path, the guest disables
>notifications after the first kick and vhost re-enables notifications
>after
>completing processing of the tx ring.  Can a similar thing be done for
>the
>receive path?  Once vhost sends the first notification for a received
>packet
>it can disable notifications and let the guest re-enable notifications
>when it
>has finished processing the receive ring.  Also, can the virtio-net
>driver do
>some adaptive polling (or does napi take care of that for the guest)?
>
>[Chaks] A better method is to have the producer generate the kick
>notifications only when the queue/ring transitions from empty to
>non-empty state. The consumer is not burdened with the task of reenabling
>the notifications. This of course assumes that notifications will never
>get lost. If loss of notifications is a possibility, producer can keep
>generating the notifications till guest signals (via some atomically
>manipulated memory variable) that it started consuming. The next
>notification will go out when the ring/queue again transitions from empty
>to non-empty state.

Chaks


============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================


  reply	other threads:[~2011-03-09  2:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 22:31 Network performance with small packets - continued Tom Lendacky
2011-03-09  2:34 ` Chigurupati, Chaks [this message]
2011-03-09  7:15 ` Michael S. Tsirkin
2011-03-09 15:45   ` Shirley Ma
2011-03-09 16:10     ` Michael S. Tsirkin
2011-03-09 16:25       ` Shirley Ma
2011-03-09 16:32         ` Michael S. Tsirkin
2011-03-09 16:38           ` Shirley Ma
2011-03-09 16:09   ` Tom Lendacky
2011-03-09 16:21     ` Shirley Ma
2011-03-09 16:28     ` Michael S. Tsirkin
2011-03-09 16:51     ` Shirley Ma
2011-03-09 17:16       ` Michael S. Tsirkin
2011-03-09 18:16         ` Shirley Ma
2011-03-09 22:51     ` Tom Lendacky
2011-03-09 20:11   ` Tom Lendacky
2011-03-09 21:56     ` Michael S. Tsirkin
2011-03-09 23:25       ` Tom Lendacky
2011-03-10  6:54         ` Michael S. Tsirkin
2011-03-10 15:23           ` Tom Lendacky
2011-03-10 15:34             ` Michael S. Tsirkin
2011-03-10 17:16               ` Tom Lendacky
2011-03-18 15:38                 ` Tom Lendacky
2011-03-10  0:59       ` Shirley Ma
2011-03-10  2:30         ` Rick Jones
2011-03-09 22:45     ` Shirley Ma
2011-03-09 22:57       ` Tom Lendacky
2011-03-09  7:17 ` Michael S. Tsirkin
2011-03-09 16:17   ` Tom Lendacky

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=C99C259E.C1A0%chaks@wichorus.com \
    --to=chaks@wichorus.com \
    --cc=kvm@vger.kernel.org \
    --cc=tahm@linux.vnet.ibm.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