netdev - Re: [PATCH][next-next][v2] netlink: avoid to allocate full skb when sending to many devices

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] [day] [month] [year] [list]

Message-ID: <CAM_iQpVeiF0OX=z7i6ohzshOvh7x1TTKh+TDn0c0xucpBCRYxQ@mail.gmail.com>
Date:   Fri, 21 Sep 2018 12:08:32 -0700
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     "Li,Rongqing" <lirongqing@...du.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH][next-next][v2] netlink: avoid to allocate full skb when
 sending to many devices

On Thu, Sep 20, 2018 at 1:58 AM Li RongQing <lirongqing@...du.com> wrote:
>
> if skb->head is vmalloc address, when this skb is delivered, full
> allocation for this skb is required, if there are many devices,
> the full allocation will be called for every devices

So why do you in practice need many netlink tap devices?

tap devices are now isolated in each netns, so at max you need
one tap device per netns in practice.