qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zwu.kernel@gmail.com
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
	jan.kiszka@web.de, stefanha@linux.vnet.ibm.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH v2] slirp: fix packet requeue issue in batchq
Date: Thu, 16 Feb 2012 16:07:14 +0800	[thread overview]
Message-ID: <1329379634-1498-1-git-send-email-zwu.kernel@gmail.com> (raw)

From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>

Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
 slirp/if.c   |   19 +++++++++++++++++--
 slirp/mbuf.c |    3 +--
 2 files changed, 18 insertions(+), 4 deletions(-)

diff --git a/slirp/if.c b/slirp/if.c
index 8e0cac2..57350d5 100644
--- a/slirp/if.c
+++ b/slirp/if.c
@@ -22,6 +22,7 @@ ifs_remque(struct mbuf *ifm)
 {
 	ifm->ifs_prev->ifs_next = ifm->ifs_next;
 	ifm->ifs_next->ifs_prev = ifm->ifs_prev;
+        ifs_init(ifm);
 }
 
 void
@@ -154,7 +155,7 @@ if_start(Slirp *slirp)
 {
     uint64_t now = qemu_get_clock_ns(rt_clock);
     int requeued = 0;
-	struct mbuf *ifm, *ifqt;
+    struct mbuf *ifm, *ifqt, *ifm_next;
 
 	DEBUG_CALL("if_start");
 
@@ -162,6 +163,8 @@ if_start(Slirp *slirp)
 	   return; /* Nothing to do */
 
  again:
+        ifm_next = NULL;
+
         /* check if we can really output */
         if (!slirp_can_output(slirp->opaque))
             return;
@@ -190,6 +193,7 @@ if_start(Slirp *slirp)
 	/* If there are more packets for this session, re-queue them */
 	if (ifm->ifs_next != /* ifm->ifs_prev != */ ifm) {
 		insque(ifm->ifs_next, ifqt);
+                ifm_next = ifm->ifs_next;
 		ifs_remque(ifm);
 	}
 
@@ -209,7 +213,18 @@ if_start(Slirp *slirp)
                 m_free(ifm);
             } else {
                 /* re-queue */
-                insque(ifm, ifqt);
+                if (ifm_next) {
+                    /*restore the original state of batchq*/
+                    remque(ifm_next);
+                    insque(ifm, ifqt);
+                    ifm_next->ifs_prev->ifs_next = ifm;
+                    ifm->ifs_prev = ifm_next->ifs_prev;
+                    ifm->ifs_next = ifm_next;
+                    ifm_next->ifs_prev = ifm;
+                } else {
+                    insque(ifm, ifqt);
+                }
+
                 requeued++;
             }
         }
diff --git a/slirp/mbuf.c b/slirp/mbuf.c
index c699c75..f429c0a 100644
--- a/slirp/mbuf.c
+++ b/slirp/mbuf.c
@@ -68,8 +68,7 @@ m_get(Slirp *slirp)
 	m->m_size = SLIRP_MSIZE - offsetof(struct mbuf, m_dat);
 	m->m_data = m->m_dat;
 	m->m_len = 0;
-        m->m_nextpkt = NULL;
-        m->m_prevpkt = NULL;
+        ifs_init(m);
         m->arp_requested = false;
         m->expiration_date = (uint64_t)-1;
 end_error:
-- 
1.7.6

             reply	other threads:[~2012-02-16  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16  8:07 zwu.kernel [this message]
2012-02-16  8:37 ` [Qemu-devel] [PATCH v2] slirp: fix packet requeue issue in batchq Jan Kiszka
2012-02-16  8:45   ` Zhi Yong Wu
2012-02-16  8:46     ` Zhi Yong Wu
2012-02-16  8:48     ` Jan Kiszka
2012-02-16  9:21       ` Zhi Yong Wu
2012-02-16  9:30         ` Zhi Yong Wu

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=1329379634-1498-1-git-send-email-zwu.kernel@gmail.com \
    --to=zwu.kernel@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=wuzhy@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;
as well as URLs for NNTP newsgroup(s).