From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Jinpu Wang <jinpu.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: RFC: FMR support in SRP
Date: Sat, 20 Sep 2014 08:24:58 +0200 [thread overview]
Message-ID: <541D1DBA.7010004@acm.org> (raw)
In-Reply-To: <CAMGffE=BG6JS7C3ZZ_pwUV3AyHDtG8i49RR2PmXZo+ZT18M5XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/19/14 18:04, Jinpu Wang wrote:
> Another question, in srp_map_finish_fmr, the desc va is set to 0,
> could you point me how SRP protect multiple rdma operation write to
> same addr? or different fmr-rkey will protect this?
Hello Jack,
As you can see in srpt_map_sg_to_ib_sge() in the SRP target driver the
virtual address (db->va) and rkey (db->key) are always used in
combination - the virtual address is never used alone. Please note that
this not only holds for FMR but also for FR. More information can be
found in paragraph "10.6.2 MEMORY REGISTRATION" in the InfiniBand
Architecture Specification.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-20 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 13:11 RFC: FMR support in SRP Jinpu Wang
[not found] ` <CAMGffEkN4OmJVi6UV7PtRYq5q3XZfJVTEaJFqvypx0W8Aq8cRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 14:04 ` Bart Van Assche
[not found] ` <541C380B.1000803-HInyCGIudOg@public.gmane.org>
2014-09-19 15:08 ` Jinpu Wang
[not found] ` <CAMGffEmjzsYsOTnaPWPr4D7TDCbwcoxM8Lr2kDNWCnBOpP5k-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 15:14 ` Bart Van Assche
[not found] ` <541C485B.60302-HInyCGIudOg@public.gmane.org>
2014-09-19 15:35 ` Jinpu Wang
[not found] ` <CAMGffE=AobYJe_r=0He-U=bH6WLSsKi_Bx-S0YeH_68gE96o7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-19 16:04 ` Jinpu Wang
[not found] ` <CAMGffE=BG6JS7C3ZZ_pwUV3AyHDtG8i49RR2PmXZo+ZT18M5XA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-20 6:24 ` Bart Van Assche [this message]
[not found] ` <541D1DBA.7010004-HInyCGIudOg@public.gmane.org>
2014-09-20 8:41 ` Jack Wang
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=541D1DBA.7010004@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=jinpu.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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