From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Somnath Kotur
<somnath.kotur-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Majd Dibbiny <majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] rdma-core: Make room for source GIDs to be added
Date: Tue, 13 Jun 2017 13:20:17 -0600 [thread overview]
Message-ID: <20170613192017.GC17727@obsidianresearch.com> (raw)
In-Reply-To: <20170613060325.GF2576-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
On Tue, Jun 13, 2017 at 09:03:25AM +0300, Leon Romanovsky wrote:
> On Tue, Jun 13, 2017 at 08:24:51AM +0530, Somnath Kotur wrote:
> > Currently sgid_index is of type 'u8' so we can't really go beyond 128
> > unique GID entries(one for each type so total of 256 GID entries).
> > Change it to u16 so atleast 4k GID entries (as many VLANs that can be added)
> > can be accomodated.
> >
> > Signed-off-by: Somnath Kotur <somnath.kotur-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
> > drivers/infiniband/core/verbs.c | 2 +-
> > include/rdma/ib_verbs.h | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
>
> What type of testing did this change get?
> According to spec, "The maximum number (N) of unicast GIDs supported per endport is
> implementation specific".
>
> mlx5 and mlx4 are limited to 128 GIDs and user will get errors if he try to set
> more than that.
At a minimum I think this patch will need to add overflow protection
on the uapi paths that cast this back to a u8, and Matan should
consider expanding sgid_index to u16 in the new uapi, whenever
possible..
.. and Somnath you should review Matan's uABI patches since you want
such a fundamental change :)
Jason
--
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:[~2017-06-13 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 2:54 [PATCH] rdma-core: Make room for source GIDs to be added Somnath Kotur
[not found] ` <20170613025451.31416-1-somnath.kotur-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-06-13 6:03 ` Leon Romanovsky
[not found] ` <20170613060325.GF2576-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-06-13 19:20 ` Jason Gunthorpe [this message]
[not found] ` <20170613192017.GC17727-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-06-14 4:26 ` Somnath Kotur
[not found] ` <CAOBf=mt3jvgZUbo8gPwzojCkmrTXz3O_9FU9CqKQaftBo1M0mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-14 8:58 ` Matan Barak
2017-06-14 4:24 ` Somnath Kotur
2017-06-13 6:43 ` Yuval Shaia
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=20170613192017.GC17727@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=somnath.kotur-dY08KVG/lbpWk0Htik3J/w@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