linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Venkateswararao Jujjuri \(JV\)" <jvrao@linux.vnet.ibm.com>,
	v9fs-developer@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org,
	"Venkateswararao Jujjuri \(JV\)" <jvrao@linux.vnet.ibm.com>
Subject: Re: [PATCH] [net/9p] Change wake_up to wake_up_all() in the virtio transport.
Date: Wed, 09 Mar 2011 14:47:27 +0530	[thread overview]
Message-ID: <877hc8sleg.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1299627564-4204-1-git-send-email-jvrao@linux.vnet.ibm.com>

On Tue,  8 Mar 2011 15:39:24 -0800, "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com> wrote:
> This fix wakes up all the threads waiting for the space on VirtIO
> ring.

It would be nice to document in commit message what error you
saw without the change. Is it that the tasks were waiting even though
there was space in the virtio ring because they didn't get woken up ?

> 
> Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
> ---
>  net/9p/trans_virtio.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/net/9p/trans_virtio.c b/net/9p/trans_virtio.c
> index 9b550ed..e90e954 100644
> --- a/net/9p/trans_virtio.c
> +++ b/net/9p/trans_virtio.c
> @@ -148,7 +148,7 @@ static void req_done(struct virtqueue *vq)
>  		if (rc != NULL) {
>  			if (!chan->ring_bufs_avail) {
>  				chan->ring_bufs_avail = 1;
> -				wake_up(chan->vc_wq);
> +				wake_up_all(chan->vc_wq);
>  			}
>  			spin_unlock_irqrestore(&chan->lock, flags);
>  			P9_DPRINTK(P9_DEBUG_TRANS, ": rc %p\n", rc);
> -- 

-aneesh

      reply	other threads:[~2011-03-09  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 23:39 [PATCH] [net/9p] Change wake_up to wake_up_all() in the virtio transport Venkateswararao Jujjuri (JV)
2011-03-09  9:17 ` Aneesh Kumar K. V [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=877hc8sleg.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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).