From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question on vhost_has_feature()
Date: Tue, 4 Mar 2014 09:56:42 +0200 [thread overview]
Message-ID: <20140304075642.GA8031@redhat.com> (raw)
In-Reply-To: <20140303194422.GA17107@linux.vnet.ibm.com>
On Mon, Mar 03, 2014 at 11:44:23AM -0800, Paul E. McKenney wrote:
> Hello, Michael,
>
> Just curious about the purpose of the rcu_dereference_index_check() in
> vhost_has_feature(). I don't see how it fits in. The closest thing
> I see if the use in handle_rx(), where it selects vq->log or NULL. But
> in that case, I would expect the usual RCU usage pattern to wrap an
> rcu_dereference() around the vq->log.
>
> Enlightenment?
>
> Thanx, Paul
Hi Paul,
Yes, it's weird. As you say the use is in handle_rx.
The way it's supposed to work is that readers take vq mutex, and
writers change the value and then take and release
vq mutex.
We did it like this because there are thinkably multiple vqs.
I tried to document it in vhost.h :
/* Readers use RCU to access memory table pointer
* log base pointer and features.
* Writers use mutex below.*/
If this is a problem, it's possible to restructure the code to avoid
this pattern for vhost_has_feature, pls let me know.
Thanks a lot for paying attention!
--
MST
next prev parent reply other threads:[~2014-03-04 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 19:44 Question on vhost_has_feature() Paul E. McKenney
2014-03-04 7:56 ` Michael S. Tsirkin [this message]
2014-03-05 1:01 ` Paul E. McKenney
2014-03-05 17:11 ` Michael S. Tsirkin
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=20140304075642.GA8031@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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