From: David Brean <David.Brean-UdXhSnd/wVw@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: strong ordering for data registered memory
Date: Wed, 11 Nov 2009 16:37:41 -0500 [thread overview]
Message-ID: <4AFB2EA5.4030804@Sun.COM> (raw)
In-Reply-To: <adaskclvta4.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
I decided to minimize the impact of an API change on the class of
applications that use the current verbs interface because those
applications can safely run on platforms that deliver optimal
performance using weak ordering for data buffers. New binaries aren't
required for this class of application.
I thought it would be more appropriate to put the burden of added
complexity on the class of applications that bypass the verbs to access
special features in the hardware. In fact, those applications are
selective about memory regions that need this special handling and would
register lots of memory without the "strong ordering' bit. How
applications determine that the platform is capable of performing the
request would be beyond the scope of the verbs, however, I suppose that
the verbs framework could check and return an error.
If there are applications that expect the hardware to support "strong
ordering" and don't check the hardware, then these might be a problem.
Do any of these exists?
By the way, if I had proposed this bit several years ago, then I would
have chosen a "weak ordering" flag. Instead, I decided to try
protecting the existing base of verbs-based software.
-David
Roland Dreier wrote:
> > Some time ago there was an email sent to this group with the subject
> > "weak ordering for data registered memory". I don't recall any action
> > resulting from this thread. So, I have a question. If a bit were
> > defined to specify "strong ordering", perhaps as a "access" flag (see
> > ibv_access_flags) and used with ibv_reg_mr(), would that be sufficient
> > for (1) client applications that need a HW "guarantee" of writing the
> > last byte of an RDMA last and (2) platform implementations that need
> > to deliver that feature?
>
> What would happen if an application asked for strong ordering and the
> adapter and/or platform is not capable of that?
>
> Weak ordering is a bit easier to handle -- the app is saying "if you can
> make things go faster, don't worry about ordering here" and a platform
> where it doesn't matter can just ignore it.
>
> - R.
> --
> 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
>
--
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:[~2009-11-11 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 20:19 strong ordering for data registered memory David Brean
[not found] ` <4AF9CACE.8070700-UdXhSnd/wVw@public.gmane.org>
2009-11-11 17:57 ` Roland Dreier
[not found] ` <adaskclvta4.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-11-11 18:16 ` Richard Frank
[not found] ` <4AFAFF7A.4090602-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-11 22:11 ` David Brean
[not found] ` <4AFB3677.6050603-UdXhSnd/wVw@public.gmane.org>
2009-11-11 22:44 ` Richard Frank
[not found] ` <4AFB3E6B.3080606-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-11 23:13 ` Jason Gunthorpe
[not found] ` <20091111231338.GZ1966-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-11-12 5:41 ` Dave Olson
2009-11-12 20:43 ` David Brean
2009-11-11 21:37 ` David Brean [this message]
[not found] ` <4AFB2EA5.4030804-UdXhSnd/wVw@public.gmane.org>
2009-11-11 23:06 ` Roland Dreier
[not found] ` <ada639gvezo.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-11-12 20:42 ` David Brean
-- strict thread matches above, loose matches on Subject: below --
2009-11-12 21:51 Caitlin Bestler
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=4AFB2EA5.4030804@Sun.COM \
--to=david.brean-udxhsnd/wvw@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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