qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Scott Tsai <scottt.tw@gmail.com>
Cc: Sven Rudolph <sven_rudolph@drewag.de>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 0/5] Fix packet queueing to allow full tap queue drain
Date: Wed, 28 Oct 2009 08:49:35 +0000	[thread overview]
Message-ID: <1256719775.5105.23.camel@blaa> (raw)
In-Reply-To: <1256700810-sup-7579@xpc65.scottt>

On Wed, 2009-10-28 at 11:36 +0800, Scott Tsai wrote:
> >         Scott, Sven, if you could test the tap-drain-queue branch from
> > my tree, that would be great:
> >   http://repo.or.cz/w/qemu/markmc.git
> > 
> > Thanks,
> > Mark. 
> 
> Mark,
> I've tested http://repo.or.cz/w/qemu/markmc.git and it indeed works
> for my test case
> (NFS through emulated smc91c111 NIC on arm-integragorcp)

Many thanks for the report and confirming the fix

> How about adding a comment in tap_send() about when
> qemu_send_packet_async() would return 0 and -1?
> 
> I'd also recommend checking for the case of qemu_send_packet_async()
> returning -1 and dropping a packet and have a debug message guarded by
> #ifdef DEBUG_TAP in case the qemu_can_send_packet() check is ever
> removed in future modifications of the code.

Yeah, it's fairly gnarly code alright. I'd prefer to make it more
obvious with something like:

  ret = qemu_send_packet_async();
  switch (ret) {
  case NET_PACKET_AGAIN:
      tap_disable_write_poll();
      return;

  case NET_PACKET_DROP:
      /* drop! */
      return;
  }

Added to my TODO list

> Also, would it be possible to get the stable-0.11 version of the patch
> into the soon to be released Fedora 12? I've written some embedded
> Linux tutorials for Taiwanese consumer electronics developers that
> recommends using qemu on Fedora. Being able to rely on NFS always
> working in Fedora's qmeu packet would really help :)

Filed https://bugzilla.redhat.com/531419 ... I'll pull it in later
today.

qemu-system-arm on F12 works okay then? That's good to know, it's the
first I've heard of someone using it :-)

Thanks,
Mark.

      reply	other threads:[~2009-10-28  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 18:16 [Qemu-devel] [PATCH 0/5] Fix packet queueing to allow full tap queue drain Mark McLoughlin
2009-10-27 18:16 ` [Qemu-devel] [PATCH 1/5] tap: disable draining queue in one go Mark McLoughlin
2009-10-27 18:16 ` [Qemu-devel] [PATCH 2/5] net: disable receiving if client returns zero Mark McLoughlin
2009-10-27 18:16 ` [Qemu-devel] [PATCH 3/5] net/queue: queue packets even if sender doesn't supply a callback Mark McLoughlin
2009-10-27 18:16 ` [Qemu-devel] [PATCH 4/5] virtio-net: split the has_buffers() logic from can_receive() Mark McLoughlin
2009-10-27 18:16 ` [Qemu-devel] [PATCH 5/5] tap: drain queue in tap_send() Mark McLoughlin
2009-10-30 16:21   ` Anthony Liguori
2009-10-30 16:34     ` Mark McLoughlin
2009-10-30 17:46       ` Anthony Liguori
2009-10-28  3:36 ` [Qemu-devel] Re: [PATCH 0/5] Fix packet queueing to allow full tap queue drain Scott Tsai
2009-10-28  8:49   ` Mark McLoughlin [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=1256719775.5105.23.camel@blaa \
    --to=markmc@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=scottt.tw@gmail.com \
    --cc=sven_rudolph@drewag.de \
    /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).