[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMinTavwbF3fbD=FDGxGCKt9DuGFPNQOJwA2mwpEHN3Ttw@mail.gmail.com>
Date: Tue, 17 Jul 2018 00:14:03 +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 mlx5-next 01/18] net/mlx5: Add proper NIC TX steering
flow tables support
On Mon, Jul 16, 2018 at 11:22 AM, Leon Romanovsky <leon@...nel.org> wrote:
> From: Mark Bloch <markb@...lanox.com>
>
> Expose the ability to add steering rules to NIC TX flow tables.
> For now, we are only adding TX bypass (egress) which is used by the RDMA
> side. While we are here clean the switch logic.
>
> We expose the same number of priorities as the RX bypass.
What is the use-case / model for priorities in TX steering?
Is/where this (tx prios) is used @ downstream patch?
Or.
Powered by blists - more mailing lists