From: "Sean Hefty" <sean.hefty@intel.com>
To: "'Caitlin Bestler'" <Caitlin.Bestler@neterion.com>,
"Joachim Fenkes" <FENKES@de.ibm.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Roland Dreier" <rdreier@cisco.com>,
"LKML" <linux-kernel@vger.kernel.org>, <linuxppc-dev@ozlabs.org>,
"OF-General" <general@lists.openfabrics.org>,
"Stefan Roscher" <stefan.roscher@de.ibm.com>
Subject: RE: [ofa-general] Re: [ewg] Re: [PATCH] IB/ehca: SerializeHCA-related hCalls on POWER5
Date: Thu, 13 Dec 2007 13:48:40 -0800 [thread overview]
Message-ID: <000301c83dd1$ec49d520$9b37170a@amr.corp.intel.com> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7702B14004@nekter>
>To clarify, an FMR Work Request is simply posted to the SendQ like
>any other Work Request (of course the QP has to be privileged, or
>it will complete in error). An SQ Post should never block.
FMR's as defined by the IB spec and that created by Mellanox are not the same.
They, unfortunately, use the same name and acronym only. Mellanox FMRs use an
API that is more like that of standard MRs.
- Sean
next prev parent reply other threads:[~2007-12-13 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 15:07 [PATCH] IB/ehca: Serialize HCA-related hCalls on POWER5 Joachim Fenkes
2007-12-06 15:48 ` Arnd Bergmann
2007-12-06 18:27 ` Roland Dreier
2007-12-07 9:58 ` Arnd Bergmann
2007-12-09 23:22 ` Roland Dreier
2007-12-10 17:41 ` Joachim Fenkes
2007-12-10 21:47 ` Roland Dreier
2007-12-11 8:38 ` Joachim Fenkes
2007-12-12 12:14 ` [ewg] " Or Gerlitz
2007-12-12 16:02 ` Christoph Raisch
2007-12-12 19:09 ` Roland Dreier
2007-12-13 8:30 ` Or Gerlitz
2007-12-13 19:22 ` [ofa-general] " Caitlin Bestler
2007-12-13 20:59 ` Joachim Fenkes
2007-12-13 21:08 ` Caitlin Bestler
2007-12-13 21:35 ` Joachim Fenkes
2007-12-13 21:48 ` Sean Hefty [this message]
2007-12-07 16:25 ` Joachim Fenkes
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='000301c83dd1$ec49d520$9b37170a@amr.corp.intel.com' \
--to=sean.hefty@intel.com \
--cc=Caitlin.Bestler@neterion.com \
--cc=FENKES@de.ibm.com \
--cc=arnd@arndb.de \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rdreier@cisco.com \
--cc=stefan.roscher@de.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;
as well as URLs for NNTP newsgroup(s).