From: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
To: "Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] IB/core: Change rdma_protcol_iboe to roce
Date: Fri, 15 May 2015 23:32:46 +0200 [thread overview]
Message-ID: <1431725566.11477.15.camel@opteya.com> (raw)
In-Reply-To: <2807E5FD2F6FDA4886F6618EAC48510E1107F5B2-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hi,
Le vendredi 15 mai 2015 à 16:29 +0000, Weiny, Ira a écrit :
> > Le jeudi 14 mai 2015 à 15:01 -0400, ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org a écrit :
> > > From: Ira Weiny <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > >
> > > It has been decided that ROCE should be used within the kernel rather
> > > than IBOE as we used before. Change iboe to roce on the new
> > rdma_protocol_* functions.
> > >
> >
> > Erk ... What's the usefulness of such patch
>
> Currently there is inconsistency in the naming of the RoCE technology.
>
> 12:27:35 > grep -r roce drivers/infiniband | grep -v Binary | grep -i -v proce | wc -l
> 85
>
> All in the driver code.
>
> 12:27:48 > grep -r iboe drivers/infiniband | grep -v Binary | wc -l
> 130
>
> Mainly in the core and mlx4 driver.
>
I see thing a bit differently:
$ grep -ri 'roce' include/rdma/ \
include/uapi/rdma \
include/uapi/linux/if_infiniband.h \
drivers/infiniband/core | grep -vi proce | wc -l
0
$ grep -ri 'iboe' include/rdma/ \
include/uapi/rdma \
include/uapi/linux/if_infiniband.h \
drivers/infiniband/core | grep -vi proce | wc -l
30
(On next-20150515).
I believe the drivers can have the names they want, especially ocrdma,
Emulex OneConnect RoCE.
> This patch was to clean up the management helper function as a general
> move toward standardizing on roce rather than iboe. Most people in
> the community refer to this as "RoCE" so that name was chosen to move
> to.
>
It's not the first time Linux use a name not matching the "vendor" one,
amd64, arm64, etc.
> >
> > IBoE is used throughout the IB/RDMA subsystem.
> >
> > Changing only these occurences is rather inconsistent.
> >
>
> I asked about changing all the references and Doug mentioned he would
> make a patch to change the other references. Personally I don't want
> to see a massive rename patch but this could be done.
>
That's my main concern: I dislike patch that change such large portion
of code, for not well defined purpose.
I think "It has been decided that ROCE should be used within" is not
enough to justify the change.
But "Most people in the community refer to this as "RoCE" so that name
was chosen to move to." sound a bit better as an explanation.
And now, I'm stopping bikeshedding :)
Regards.
--
Yann Droneaud
OPTEYA
--
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:[~2015-05-15 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:01 [PATCH] IB/core: Change rdma_protcol_iboe to roce ira.weiny-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1431630106-28829-1-git-send-email-ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-05-15 15:14 ` Yann Droneaud
[not found] ` <1431702851.4214.3.camel-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2015-05-15 16:29 ` Weiny, Ira
[not found] ` <2807E5FD2F6FDA4886F6618EAC48510E1107F5B2-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-05-15 21:32 ` Yann Droneaud [this message]
[not found] ` <1431725566.11477.15.camel-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2015-05-18 15:08 ` Doug Ledford
2015-05-18 16:15 ` Parav Pandit
[not found] ` <cdc5efd8a350e6a98c98f5f8169fe487-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-20 18:58 ` Doug Ledford
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=1431725566.11477.15.camel@opteya.com \
--to=ydroneaud-rly5vtjfyj3qt0dzr+alfa@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@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