netdev - Re: [PATCH RFC (resend) net-next 0/6] virtio-net: Add support for virtio-net header extensions

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: <20170424200232-mutt-send-email-mst@kernel.org>
Date:   Mon, 24 Apr 2017 20:04:43 +0300
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     Vlad Yasevich <vyasevic@...hat.com>
Cc:     Jason Wang <jasowang@...hat.com>,
        Vladislav Yasevich <vyasevich@...il.com>,
        netdev@...r.kernel.org, virtio-dev@...ts.oasis-open.org,
        maxime.coquelin@...hat.com,
        virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH RFC (resend) net-next 0/6] virtio-net: Add support for
 virtio-net header extensions

On Thu, Apr 20, 2017 at 11:34:57AM -0400, Vlad Yasevich wrote:
> > - For 1.1, do we really want something like vnet header? AFAIK, it was not used by modern
> > NICs, is this better to pack all meta-data into descriptor itself? This may need a some
> > changes in tun/macvtap, but looks more PCIE friendly.
> 
> That would really be ideal and I've looked at this.

We already have at least 16 unused bits in the used ring
(head is 16 bit we are using 32 for it).

-- 
MST