netdev - Re: [oss-drivers] Re: [PATCH net-next v2 0/7] devlink: expose PF and VF representors as ports

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: <20190302114939.45d878fc@cakuba.netronome.com>
Date:   Sat, 2 Mar 2019 11:49:39 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Jiri Pirko <jiri@...nulli.us>
Cc:     davem@...emloft.net, netdev@...r.kernel.org,
        oss-drivers@...ronome.com
Subject: Re: [oss-drivers] Re: [PATCH net-next v2 0/7] devlink: expose PF
 and VF representors as ports

On Sat, 2 Mar 2019 11:13:37 +0100, Jiri Pirko wrote:
> >This is the conceptual image of devlink instances:
> >
> >                    HOST A             ||          HOST B
> >                                       ||
> >        PF A       | V | V | V | V     ||       PF B        | V | V | V
> >                   |*F |*F |*F |*F ... ||                   |*F |*F |*F
> >*port A0 |*port A1 | 0 | 1 | 2 | 3     ||*port B0 |*port B1 | 0 | 1 | 2
> >                                       ||
> >             PCI Express link          ||        PCI Express link
> >        \      \      \  |   |   |          |       |      /   /   /
> >         \      \      \ |   |   |          |       |     /   /   /
> >      /\  \______\______\'___|___|__________|_______'____/___/___/__    /\
> >      ||  |+PF0s0|+PF0s1 |+VF0|+VF1| ...|   |+PF1s0|+PF1s1|+VF0|+VF1|   ||
> >  i   ||  |------ ------ ----- ---- ----|--- ------ ------ ---- ----|   ||   i
> >d n H ||  |               <<==========                              |   || d n H
> >e s O ||  |                            ==========>>                 |   || e s O
> >v t S ||  |                    SR-IOV e-switch                      |   || v t S
> >l a T ||  |               <<==========                              |   || l a T
> >i n   ||  |                            ==========>>                 |   || i n
> >n c A ||  |               ________ _________ ________               |   || n c B
> >k e   ||  |              |+Phys 0 |+Phys 1  |+Phys 2 |              |   || k e
> >      ||  \---------------------------------------------------------/   ||
> >      \/                      |        |         |                      \/
> >                              |        |         |
> >                                 ||         ||
> >                          MAC 0  ||  MAC 1  || MAC 2
> >                                 ||         ||
> >
> > '+' marks the devlink ports and port (-representor-) netdevs
> > '*' marks host netdevs (actual VF/PF netdev)  
> 
> As I wrote in the reply to patch 4, I think we need to figure out if we
> want to model all entities that belong under specific devlink
> instance/pci address - which I prefer, or we want to have only eswitch
> ports there.
> 
> One way or another, I think that it is not good idea to merge this
> patchset this late, I would prefer to wait for next net-next opening...
> In the meantime we can sync and make this whole thing crystal clear, for
> everyone.

Makes sense, let's keep talking.