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: <20180403180716.66c3daee@redhat.com>
Date:   Tue, 3 Apr 2018 18:07:16 +0200
From:   Jesper Dangaard Brouer <brouer@...hat.com>
To:     David Miller <davem@...emloft.net>
Cc:     netdev@...r.kernel.org, bjorn.topel@...el.com,
        magnus.karlsson@...el.com, eugenia@...lanox.com,
        jasowang@...hat.com, john.fastabend@...il.com, eranbe@...lanox.com,
        saeedm@...lanox.com, galp@...lanox.com, borkmann@...earbox.net,
        alexei.starovoitov@...il.com, tariqt@...lanox.com,
        brouer@...hat.com
Subject: Re: [net-next V9 PATCH 00/16] XDP redirect memory return API

On Tue, 03 Apr 2018 10:54:27 -0400 (EDT)
David Miller <davem@...emloft.net> wrote:

> From: Jesper Dangaard Brouer <brouer@...hat.com>
> Date: Tue, 03 Apr 2018 13:07:36 +0200
> 
> > This is V9, but it's worth mentioning that V8 was send against
> > net-next, because i40e got XDP_REDIRECT support in-between V6, and it
> > doesn't exist in bpf-next yet.  Most significant change in V8 was that
> > page_pool only gets compiled into the kernel when a drivers Kconfig
> > 'select' the feature.  
> 
> Jesper, this series now looks good to me, however the net-next tree is
> closed at this point.

I noticed, but though that in-flight patchset's were still allowed...

> 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?
... 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.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer