From: Paolo Bonzini <pbonzini@redhat.com>
To: zwu.kernel@gmail.com
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
stefanha@linux.vnet.ibm.com, jan.kiszka@siemens.com,
wuzhy@linux.vnet.ibm.com
Subject: Re: [PATCH v4 16/16] hub: add the support for hub own flow control
Date: Fri, 25 May 2012 13:05:23 +0200 [thread overview]
Message-ID: <4FBF6773.2080306@redhat.com> (raw)
In-Reply-To: <1337943134-1107-1-git-send-email-zwu.kernel@gmail.com>
Il 25/05/2012 12:52, zwu.kernel@gmail.com ha scritto:
> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>
> Only when all other hub port's *peer* .can_receive() all return 1, the source hub port .can_receive() return 1.
>
> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
> ---
> net/hub.c | 27 ++++++++++++++++++++++++---
> 1 files changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/net/hub.c b/net/hub.c
> index 357ca87..478cce1 100644
> --- a/net/hub.c
> +++ b/net/hub.c
> @@ -15,6 +15,7 @@
> #include "monitor.h"
> #include "net.h"
> #include "hub.h"
> +#include "iov.h"
>
> /*
> * A hub broadcasts incoming packets to all its ports except the source port.
> @@ -59,16 +60,16 @@ static ssize_t net_hub_receive_iov(NetHub *hub, NetHubPort *source_port,
> const struct iovec *iov, int iovcnt)
> {
> NetHubPort *port;
> - ssize_t ret = 0;
> + ssize_t len = iov_size(iov, iovcnt);
>
> QLIST_FOREACH(port, &hub->ports, next) {
> if (port == source_port) {
> continue;
> }
>
> - ret = qemu_sendv_packet(&port->nc, iov, iovcnt);
> + qemu_sendv_packet(&port->nc, iov, iovcnt);
I think you still need to apply flow control, otherwise you're cheating.
But perhaps this is acceptable, I'll leave it to more expert people.
Paolo
next prev parent reply other threads:[~2012-05-25 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 10:52 [PATCH v4 16/16] hub: add the support for hub own flow control zwu.kernel
2012-05-25 11:05 ` Paolo Bonzini [this message]
2012-05-25 11:10 ` Zhi Yong Wu
2012-05-25 12:13 ` Stefan Hajnoczi
2012-05-26 12:32 ` 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=4FBF6773.2080306@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.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