From: "Steve Wise" <swise@opengridcomputing.com>
To: "'Bart Van Assche'" <bvanassche@acm.org>, <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<tom@opengridcomputing.com>
Subject: RE: [PATCH] svcrdma: Fence LOCAL_INV work requests
Date: Thu, 5 Jun 2014 08:55:31 -0500 [thread overview]
Message-ID: <002901cf80c5$d0b577e0$722067a0$@opengridcomputing.com> (raw)
In-Reply-To: <53901ADB.9020405@acm.org>
> -----Original Message-----
> From: Bart Van Assche [mailto:bvanassche@acm.org]
> Sent: Thursday, June 05, 2014 2:23 AM
> To: Steve Wise; bfields@fieldses.org
> Cc: linux-nfs@vger.kernel.org; linux-rdma@vger.kernel.org; tom@opengridcomputing.com
> Subject: Re: [PATCH] svcrdma: Fence LOCAL_INV work requests
>
> On 06/02/14 19:14, Steve Wise wrote:
> > Fencing forces the invalidate to only happen after all subsequent send
> > work requests have been completed.
>
> Shouldn't that read "prior" instead of "subsequent" ?
>
Yes.
next prev parent reply other threads:[~2014-06-05 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 17:14 [PATCH] svcrdma: Fence LOCAL_INV work requests Steve Wise
2014-06-05 5:29 ` Devesh Sharma
2014-06-05 7:23 ` Bart Van Assche
2014-06-05 13:55 ` Steve Wise [this message]
2014-06-05 15:00 ` Steve Wise
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='002901cf80c5$d0b577e0$722067a0$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=bvanassche@acm.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tom@opengridcomputing.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).