[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiLrSZMqZTSySB+PwUsXoHfh99QJZ+_WdQQn4sgA2HYNQ@mail.gmail.com>
Date: Tue, 17 Jul 2018 00:23:54 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Mark Bloch <markb@...lanox.com>
Cc: Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Leon Romanovsky <leonro@...lanox.com>,
RDMA mailing list <linux-rdma@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>,
linux-netdev <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH rdma-next 13/18] RDMA/mlx5: Enable decap and packet
reformat on flow tables
On Mon, Jul 16, 2018 at 11:23 AM, Leon Romanovsky <leon@...nel.org> wrote:
> From: Mark Bloch <markb@...lanox.com>
>
> If NIC RX flow tables support decap opertion, enable it on creation.
opertion --> operation
> If NIC TX flow tables support reformat opertion, enable it on creation.
What is the trigger to use the decap flag on RX table or encap flag on
TX table?
Please note that we have a short blanket w.r.t mutual usage by
NIC vs e-Switch steering, did you consider to do that on demand?
Powered by blists - more mailing lists