From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Liran Liss <liranl-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Cc: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCHv7 0/9] RoCEE support to Infiniband
Date: Wed, 13 Jan 2010 13:18:37 -0800 [thread overview]
Message-ID: <adaockxn1oy.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <2ED289D4E09FBD4D92D911E869B97FDD026854EA-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org> (Liran Liss's message of "Wed, 13 Jan 2010 23:08:30 +0200")
> RoCEE was chosen for these patches in accordance with the terminology
> used in the proposal discussed by the OFA. We have no problem
> resubmitting these patches using "iboe" so that you can push them into
> 2.6.34. We will need to stay aware of any future name recommendations
> by relevant industry bodies.
Well, don't just take my opinion as the final answer. It would be good
if someone could "officially" pick a name. However I really do feel
that RoCEE is a pretty bad choice, since it is both technically
inaccurate and also hard for users to understand.
- 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
prev parent reply other threads:[~2010-01-13 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 10:32 [PATCHv7 0/9] RoCEE support to Infiniband Eli Cohen
2010-01-12 17:12 ` Roland Dreier
[not found] ` <ada7hrnp7rr.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-13 21:08 ` Liran Liss
[not found] ` <2ED289D4E09FBD4D92D911E869B97FDD026854EA-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org>
2010-01-13 21:18 ` Roland Dreier [this message]
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=adaockxn1oy.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liranl-VPRAkNaXOzVS1MOuV/RT9w@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