[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMjcB=8QSEg1hXrKd4m8HF11Ttf2Pw_bRP17p9MJEte-GA@mail.gmail.com>
Date: Thu, 20 Sep 2018 23:16:01 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Leon Romanovsky <leonro@...lanox.com>,
RDMA mailing list <linux-rdma@...r.kernel.org>,
Yishai Hadas <yishaih@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>,
linux-netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH rdma-next v1 0/7] Preparation to DevX extension series
On Thu, Sep 20, 2018 at 9:35 PM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...lanox.com>
> Set uid as part of various IB commands so that the firmware can manage
> the IB object in a secured way.
This series deals with FS core and commands used by the Ethernet driver
> net/mlx5: Update mlx5_ifc with DEVX UID bits
> net/mlx5: Set uid as part of CQ commands
> net/mlx5: Set uid as part of RQ commands
> net/mlx5: Set uid as part of SQ commands
such as the life-cycle (create, modify, destroy) of objects like:
RQ/SQ/CQ/etc --
saying IB commands is inaccurate, please be more precise
>
> The firmware should mark this IB object with the given uid so that it
> can be used later on only by objects with the same uid.
these are not IB objects, but rather Ethernet objects
>
> Upon DEVX flows that use this objec, the pointed object must have
> the same uid as of the issuer uid command.
typo - objec --> object
>
> When a command is issued with uid=0 it means that the issuer of the
> command is trusted (i.e. kernel), in that case any pointed object
> can be used regardless of its uid.
>
> Thanks
>
> net/mlx5: Set uid as part of SRQ commands
> net/mlx5: Set uid as part of DCT commands
> net/mlx5: Set uid as part of QP commands
Powered by blists - more mailing lists