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: <20190627154206.5d458e94@cakuba.netronome.com>
Date:   Thu, 27 Jun 2019 15:42:06 -0700
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Jonathan Lemon <jonathan.lemon@...il.com>
Cc:     <netdev@...r.kernel.org>, <bjorn.topel@...el.com>,
        <magnus.karlsson@...el.com>, <saeedm@...lanox.com>,
        <maximmi@...lanox.com>, <brouer@...hat.com>, <kernel-team@...com>
Subject: Re: [PATCH 4/6 bfp-next] Simplify AF_XDP umem allocation path for
 Intel drivers.

On Thu, 27 Jun 2019 15:08:34 -0700, Jonathan Lemon wrote:
> Now that the recycle stack is always used for the driver umem path, the
> driver code path can be simplified.
> 
> Signed-off-by: Jonathan Lemon <jonathan.lemon@...il.com>

I guess it's a question to Bjorn and Magnus whether they want Intel
drivers to always go through the reuse queue..

Could you be more explicit on the motivation?  I'd call this patch set
"make all drivers use reuse queue" rather than "clean up".

Also when you're changing code please make sure you CC the author.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ