[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJbaOR5HpoaQLHoBGhariTACf-OLKRWqP3KBacvOUgGdg@mail.gmail.com>
Date: Tue, 21 Jun 2016 08:18:49 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Saeed Mahameed <saeedm@....mellanox.co.il>
Cc: Alexei Starovoitov <alexei.starovoitov@...il.com>,
Saeed Mahameed <saeedm@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Doug Ledford <dledford@...hat.com>,
Or Gerlitz <ogerlitz@...lanox.com>,
Maor Gottlieb <maorg@...lanox.com>,
Huy Nguyen <huyn@...lanox.com>, Tal Alon <talal@...lanox.com>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next 12/18] IB/mlx5: Add kernel offload flow-tag
On Tue, Jun 21, 2016 at 6:04 AM, Saeed Mahameed
<saeedm@....mellanox.co.il> wrote:
>
> Alexei , I don't understand your concern.
> We already have a full/complete working dpdk bypass solution in
> userspace nothing extra is required from the kernel.
>
> We just want to see this traffic and any other rdma traffic in tcpdump
> or other standard sniffing tools.
>
> Anyway we brainstormed this internally today and we don't like the
> "skb->protocol = 0xffff" solution,
One solution would be to setup a special netdev used only for sniffers
(No IP address on it)
-> Only changes would happen in the driver, to set skb->dev to this
'debug' device.
Powered by blists - more mailing lists