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]
Date:   Sat, 25 Jul 2020 09:39:07 -0700
From:   Tom Herbert <>
To:     Jakub Kicinski <>
Cc:     "Venkataramanan, Anirudh" <>,
        "Wang, Haiyue" <>,
        "" <>,
        "" <>,
        "" <>,
        "Bowers, AndrewX" <>,
        "Kirsher, Jeffrey T" <>,
        "" <>,
        "Nguyen, Anthony L" <>,
        "Lu, Nannan" <>
Subject: Re: [net-next 1/5] ice: add the virtchnl handler for AdminQ command

On Wed, Jul 22, 2020 at 6:07 PM Jakub Kicinski <> wrote:
> On Thu, 23 Jul 2020 00:37:29 +0000 Venkataramanan, Anirudh wrote:
> > Can you please clarify how you (and the community) define bifurcated
> > driver?
> No amount of clarification from me will change the fact that you need
> this for DPDK.


The fundamental problem we have wrt DPDK is that they are not just
satisfied to just bypass the kernel datapath, they are endeavouring to
bypass the kernel control path as well with things like RTE flow API.
The purpose of this patch set, AFAICT, is to keep the kernel in the
control plane path so that we can maintain one consistent management
view of device resources. The unpleasant alternative is that DPDK will
send control messages directly to the device thereby bypassing the
kernel control plane and thus resulting in two independent entities
managing the same device and forcing a bifurcated control plane in the
device (which of course results in a complete mess!).


Powered by blists - more mailing lists