virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio: don't always force a notification when ring is full
Date: Thu, 19 Jun 2008 10:14:34 +0200	[thread overview]
Message-ID: <200806191014.34741.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200806190940.57083.rusty@rustcorp.com.au>

Am Donnerstag, 19. Juni 2008 schrieb Rusty Russell:
> We force notification when the ring is full, even if the host has
> indicated it doesn't want to know.  This seemed like a good idea at
> the time: if we fill the transmit ring, we should tell the host
> immediately.
> 
> Unfortunately this logic also applies to the receiving ring, which is
> refilled constantly.  We should introduce real notification thesholds
> to replace this logic.  Meanwhile, removing the logic altogether breaks
> the heuristics which KVM uses, so we use a hack: only notify if there are
> outgoing parts of the new buffer.


I did not yet finish the VIRTIO_F_NOTIFY_ON_EMPTY implementation for s390, so 
I cant tell for sure if it makes a difference.

Nevertheless, the patch looks good to me.

      parent reply	other threads:[~2008-06-19  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 23:40 [PATCH] virtio: don't always force a notification when ring is full Rusty Russell
2008-06-19  0:40 ` Anthony Liguori
2008-06-19  8:14 ` Christian Borntraeger [this message]

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=200806191014.34741.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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).