From: Sean Hefty <mshefty@ichips.intel.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] Re: RFC: ipath ioctls and their replacements
Date: Thu, 19 Jan 2006 16:02:16 -0800 [thread overview]
Message-ID: <43D02888.30605@ichips.intel.com> (raw)
In-Reply-To: <1137714259.22241.12.camel@localhost.localdomain>
Bryan O'Sullivan wrote:
> We are not really in the RDMA camp. Our facility looks more like "when
> this kind of message comes in, be sure that it shows up at this point in
> my address space", which does not match RDMA semantics.
A lot of people mean QP-like semantics when they talk about "RDMA", rather than
the RDMA operation itself. I.e. pre-posted receive buffers associated with a
particular user-space process.
That aside, conceptually, I see little difference between RDMA semantics versus
the facility that you describe. The main difference is the complexity of the
header and the checks done against it.
- Sean
next prev parent reply other threads:[~2006-01-20 0:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:43 RFC: ipath ioctls and their replacements Bryan O'Sullivan
2006-01-19 0:48 ` David S. Miller
2006-01-19 1:14 ` Bryan O'Sullivan
2006-01-19 1:17 ` David S. Miller
2006-01-19 5:17 ` Bryan O'Sullivan
2006-01-19 5:43 ` Greg KH
2006-01-19 0:53 ` Greg KH
2006-01-19 1:17 ` Bryan O'Sullivan
2006-01-19 2:54 ` Greg KH
2006-01-19 2:57 ` Greg KH
2006-01-19 3:49 ` Andrew Morton
2006-01-19 4:03 ` Greg KH
2006-01-19 5:02 ` Bryan O'Sullivan
2006-01-19 5:39 ` Greg KH
2006-01-19 5:53 ` Bryan O'Sullivan
2006-01-19 22:57 ` Greg KH
2006-01-19 23:44 ` Bryan O'Sullivan
2006-01-20 0:02 ` Sean Hefty [this message]
2006-01-19 8:25 ` Eric W. Biederman
2006-01-19 8:39 ` David S. Miller
2006-02-24 20:19 ` [PATCH 1/1] Topology c fix Zachary Amsden
2006-02-25 0:17 ` Andrew Vasquez
2006-01-19 16:29 ` RFC: ipath ioctls and their replacements Bryan O'Sullivan
2006-01-19 18:20 ` Eric W. Biederman
2006-01-19 18:50 ` [openib-general] " Sean Hefty
2006-01-19 18:55 ` Bryan O'Sullivan
2006-01-19 20:31 ` Eric W. Biederman
2006-01-19 21:53 ` Bryan O'Sullivan
2006-01-19 21:08 ` Sean Hefty
2006-01-19 21:52 ` Bryan O'Sullivan
2006-01-19 18:50 ` Bryan O'Sullivan
2006-01-19 20:29 ` Eric W. Biederman
2006-01-19 20:47 ` [openib-general] " Steve Wise
2006-01-19 22:13 ` Bryan O'Sullivan
2006-01-21 4:40 ` Roland Dreier
2006-01-25 22:32 ` Bryan O'Sullivan
2006-01-25 22:43 ` [openib-general] " Muli Ben-Yehuda
2006-01-25 22:55 ` Bryan O'Sullivan
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=43D02888.30605@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.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).