virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Amit Shah <amit.shah@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/8] virtio: console: Fixes, cleanups, stats for bytes transferred
Date: Tue, 01 Nov 2011 10:27:44 +1030	[thread overview]
Message-ID: <8739e8ww7b.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111031101940.GC3557@amit-x200.redhat.com>

On Mon, 31 Oct 2011 15:49:40 +0530, Amit Shah <amit.shah@redhat.com> wrote:
> On (Wed) 14 Sep 2011 [13:06:38], Amit Shah wrote:
> > Hello,
> > 
> > These patches are mostly cleanups (patches 1, 4, 5, 6, 7).  Patches 2
> > and 3 fix cases which will be exposed when S4 support is enabled.
> > 
> > Patch 8 adds stats for bytes received, sent and discarded for each
> > port.  These are added for debugging data loss issues (rather,
> > pointing out they don't exist).  Closing a port while data transfer is
> > ongoing resulted in discarding of any pending data in the vq, which is
> > the expected case.  Adding these stats just helps showing there's no
> > data loss, but things are working as they were designed.
> > 
> > Please apply.
> 
> Hey Rusty,
> 
> Can you push this series to Linus for 3.2?  Thanks!

Yep, was going to do it yesterday but spent the day chasing console
breakage in lguest, but it's not caused by these.

Thanks,
Rusty.

      reply	other threads:[~2011-10-31 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1315985553.git.amit.shah@redhat.com>
2011-10-31 10:19 ` [PATCH 0/8] virtio: console: Fixes, cleanups, stats for bytes transferred Amit Shah
2011-10-31 23:57   ` Rusty Russell [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=8739e8ww7b.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=amit.shah@redhat.com \
    --cc=quintela@redhat.com \
    --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).