netdev - Re: [net-next V9 PATCH 00/16] XDP redirect memory return API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALzJLG8bbMnBWvnKP-OvhZ2NF2=KzHVqyuiepnsJRQEMv86_JQ@mail.gmail.com>
Date:   Tue, 3 Apr 2018 10:03:48 -0700
From:   Saeed Mahameed <saeedm@....mellanox.co.il>
To:     David Miller <davem@...emloft.net>
Cc:     Jesper Dangaard Brouer <brouer@...hat.com>,
        Linux Netdev List <netdev@...r.kernel.org>,
        bjorn.topel@...el.com, magnus.karlsson@...el.com,
        Eugenia Emantayev <eugenia@...lanox.com>, jasowang@...hat.com,
        John Fastabend <john.fastabend@...il.com>,
        Eran Ben Elisha <eranbe@...lanox.com>,
        Saeed Mahameed <saeedm@...lanox.com>,
        Gal Pressman <galp@...lanox.com>,
        Daniel Borkmann <borkmann@...earbox.net>,
        Alexei Starovoitov <alexei.starovoitov@...il.com>,
        Tariq Toukan <tariqt@...lanox.com>
Subject: Re: [net-next V9 PATCH 00/16] XDP redirect memory return API

On Tue, Apr 3, 2018 at 9:23 AM, David Miller <davem@...emloft.net> wrote:
> From: Jesper Dangaard Brouer <brouer@...hat.com>
> Date: Tue, 3 Apr 2018 18:07:16 +0200
>
>> On Tue, 03 Apr 2018 10:54:27 -0400 (EDT)
>> David Miller <davem@...emloft.net> wrote:
>>
>>> Don't worry, just resubmit when net-next opens back up.
>>
>> At that point in time, should I got back to posting it against the
>> bpf-next git-tree again? Any preferences from Mellanox or BPF-guys?
>
> I have no personal preference, although it's probably best to go
> through the bpf-next tree.
>
>> ... It have been a bit of a pain to keep track of driver changes in
>> net-next, and waiting for them to get merged into bpf-next.
>
> I totally understand :)

it depends on how often bpf-next gets synced with net-next, mlx5
constantly changes and
I can't gurantee no merge conflicts will occur.
IMHO, this series is more focused on device drivers and less on XDP or BPF,
so it makes more sense to post it to net-next, it will be less pain
for everyone,
especially for you Jesper :).