netdev - Re: [net-next PATCH] mqprio: Reserve last 32 classid values for HW traffic classes and misc IDs

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: <20171016.205404.135809744834188625.davem@davemloft.net>
Date:   Mon, 16 Oct 2017 20:54:04 +0100 (WEST)
From:   David Miller <davem@...emloft.net>
To:     alexander.duyck@...il.com
Cc:     jiri@...nulli.us, amritha.nambiar@...el.com,
        vinicius.gomes@...el.com, netdev@...r.kernel.org, jhs@...atatu.com,
        jesus.sanchez-palencia@...el.com
Subject: Re: [net-next PATCH] mqprio: Reserve last 32 classid values for HW
 traffic classes and misc IDs

From: Alexander Duyck <alexander.duyck@...il.com>
Date: Thu, 12 Oct 2017 11:38:45 -0700

> From: Alexander Duyck <alexander.h.duyck@...el.com>
> 
> This patch makes a slight tweak to mqprio in order to bring the
> classid values used back in line with what is used for mq. The general idea
> is to reserve values :ffe0 - :ffef to identify hardware traffic classes
> normally reported via dev->num_tc. By doing this we can maintain a
> consistent behavior with mq for classid where :1 - :ffdf will represent a
> physical qdisc mapped onto a Tx queue represented by classid - 1, and the
> traffic classes will be mapped onto a known subset of classid values
> reserved for our virtual qdiscs.
> 
> Note I reserved the range from :fff0 - :ffff since this way we might be
> able to reuse these classid values with clsact and ingress which would mean
> that for mq, mqprio, ingress, and clsact we should be able to maintain a
> similar classid layout.
> 
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...el.com>

Applied, thanks Alexander.