From: Dominique Martinet <dominique.martinet@cea.fr>
To: Eric Van Hensbergen <ericvh@gmail.com>,
linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [V9fs-developer] [PATCH] 9P: Add memory barriers to protect request fields over cb/rpc threads handoff
Date: Wed, 29 Jan 2014 19:16:39 +0100 [thread overview]
Message-ID: <20140129181639.GA19138@nautica> (raw)
In-Reply-To: <1389979860-7821-2-git-send-email-dominique.martinet@cea.fr>
Hi,
Dominique Martinet wrote on Fri, Jan 17, 2014 :
> We need barriers to guarantee this pattern works as intended:
> [w] req->rc, 1 [r] req->status, 1
> wmb rmb
> [w] req->status, 1 [r] req->rc
>
> Where the wmb ensures that rc gets written before status,
> and the rmb ensures that if you observe status == 1, rc is the new value.
>
> Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
> ---
> include/net/9p/client.h | 2 +-
> net/9p/client.c | 16 +++++++++++++++-
> net/9p/trans_fd.c | 15 ++++++---------
> net/9p/trans_rdma.c | 3 +--
> net/9p/trans_virtio.c | 3 +--
> 5 files changed, 24 insertions(+), 15 deletions(-)
Reminder to get some attention now that the pull request for merge
window has passed :)
Please ask if this needs a resend, but should still apply as is.
Would be particularily nice to get confirmation that this doesn't slow
everything down for tcp/virtio folk or raises another kind of blocker
(although I have nothing better short of another transport-specific
function call after the p9_client_rpc wait is over, which is worse than
this to me, but suggestions are always welcome!)
Cheers,
--
Dominique Martinet
prev parent reply other threads:[~2014-01-29 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 17:30 [PATCH 0/1] 9P: Add memory barriers to protect request fields over cb/rpc threads handoff Dominique Martinet
2014-01-17 17:31 ` [PATCH] " Dominique Martinet
2014-01-29 18:16 ` Dominique Martinet [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=20140129181639.GA19138@nautica \
--to=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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).