netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>, Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Mark Bloch <mbloch@nvidia.com>,
	"Adit Ranadive" <aditr@vmware.com>,
	Ariel Elior <aelior@marvell.com>,
	"Bart Van Assche" <bvanassche@acm.org>,
	Bernard Metzler <bmt@zurich.ibm.com>,
	Christian Benvenuti <benve@cisco.com>,
	Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
	Devesh Sharma <devesh.sharma@broadcom.com>,
	"Latif, Faisal" <faisal.latif@intel.com>,
	"Gal Pressman" <galpress@amazon.com>,
	Jakub Kicinski <kuba@kernel.org>, Lijun Ou <oulijun@huawei.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Michal Kalderon <mkalderon@marvell.com>,
	"Mike Marciniszyn" <mike.marciniszyn@cornelisnetworks.com>,
	Naresh Kumar PBS <nareshkumar.pbs@broadcom.com>,
	Nelson Escobar <neescoba@cisco.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Potnuri Bharat Teja <bharat@chelsio.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Selvin Xavier <selvin.xavier@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
	"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
	"VMware PV-Drivers" <pv-drivers@vmware.com>,
	Weihang Li <liweihang@huawei.com>,
	"Wei Hu(Xavier)" <huwei87@hisilicon.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	"Zhu Yanjun" <zyjzyj2000@gmail.com>
Subject: RE: [PATCH rdma-next] RDMA: Support more than 255 rdma ports
Date: Mon, 29 Mar 2021 13:36:08 +0000	[thread overview]
Message-ID: <24e5759118f746c18539fc5fc0b4c706@intel.com> (raw)
In-Reply-To: <20210326131934.GA832996@nvidia.com>

> Subject: Re: [PATCH rdma-next] RDMA: Support more than 255 rdma ports
> 
> On Mon, Mar 01, 2021 at 09:04:20AM +0200, Leon Romanovsky wrote:
> > From: Mark Bloch <mbloch@nvidia.com>
> >
> > Current code uses many different types when dealing with a port of a
> > RDMA device: u8, unsigned int and u32. Switch to u32 to clean up the
> > logic.
> >
> > This allows us to make (at least) the core view consistent and use the
> > same type. Unfortunately not all places can be converted. Many uverbs
> > functions expect port to be u8 so keep those places in order not to break
> UAPIs.
> > HW/Spec defined values must also not be changed.
> >
> > With the switch to u32 we now can support devices with more than 255
> > ports. U32_MAX is reserved to make control logic a bit easier to deal
> > with. As a device with U32_MAX ports probably isn't going to happen
> > any time soon this seems like a non issue.
> >
> > When a device with more than 255 ports is created uverbs will report
> > the RDMA device as having 255 ports as this is the max currently supported.
> >
> > The verbs interface is not changed yet because the IBTA spec limits
> > the port size in too many places to be u8 and all applications that
> > relies in verbs won't be able to cope with this change. At this stage,
> > we are extending the interfaces that are using vendor channel solely
> >
> > Once the limitation is lifted mlx5 in switchdev mode will be able to
> > have thousands of SFs created by the device. As the only instance of
> > an RDMA device that reports more than 255 ports will be a representor
> > device and it exposes itself as a RAW Ethernet only device
> > CM/MAD/IPoIB and other ULPs aren't effected by this change and their
> > sysfs/interfaces that are exposes to userspace can remain unchanged.
> >
> > While here cleanup some alignment issues and remove unneeded sanity
> > checks (mainly in rdmavt),
> >
> > Signed-off-by: Mark Bloch <mbloch@nvidia.com>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > ---
> 
> Applied to for-next, I suppose this means the irdma driver needs re-spinning
> already.
> 

Sure.

      reply	other threads:[~2021-03-29 13:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  7:04 [PATCH rdma-next] RDMA: Support more than 255 rdma ports Leon Romanovsky
2021-03-01 12:48 ` Jason Gunthorpe
2021-03-01 14:44   ` Leon Romanovsky
2021-03-25  7:49 ` Leon Romanovsky
2021-03-26 13:19 ` Jason Gunthorpe
2021-03-29 13:36   ` Saleem, Shiraz [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=24e5759118f746c18539fc5fc0b4c706@intel.com \
    --to=shiraz.saleem@intel.com \
    --cc=aditr@vmware.com \
    --cc=aelior@marvell.com \
    --cc=benve@cisco.com \
    --cc=bharat@chelsio.com \
    --cc=bmt@zurich.ibm.com \
    --cc=bvanassche@acm.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.com \
    --cc=faisal.latif@intel.com \
    --cc=galpress@amazon.com \
    --cc=huwei87@hisilicon.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=liweihang@huawei.com \
    --cc=mbloch@nvidia.com \
    --cc=mike.marciniszyn@cornelisnetworks.com \
    --cc=mkalderon@marvell.com \
    --cc=nareshkumar.pbs@broadcom.com \
    --cc=neescoba@cisco.com \
    --cc=netdev@vger.kernel.org \
    --cc=oulijun@huawei.com \
    --cc=pv-drivers@vmware.com \
    --cc=saeedm@nvidia.com \
    --cc=selvin.xavier@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=sriharsha.basavapatna@broadcom.com \
    --cc=target-devel@vger.kernel.org \
    --cc=yishaih@nvidia.com \
    --cc=zyjzyj2000@gmail.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).