netdev - Re: [net-next PATCH 0/2] Add support for passing more information in mqprio offload

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: <20170315.152044.339627206478364951.davem@davemloft.net>
Date:   Wed, 15 Mar 2017 15:20:44 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     alexander.duyck@...il.com
Cc:     netdev@...r.kernel.org, thomas.lendacky@....com,
        bkenward@...arflare.com, amritha.nambiar@...el.com,
        madalin.bucur@....com, w-kwok2@...com, saeedm@...lanox.com,
        ariel.elior@...ium.com, m-karicheri2@...com,
        jeffrey.t.kirsher@...el.com, Yuval.Mintz@...ium.com,
        ecree@...arflare.com, michael.chan@...adcom.com,
        tariqt@...lanox.com
Subject: Re: [net-next PATCH 0/2] Add support for passing more information
 in mqprio offload

From: Alexander Duyck <alexander.duyck@...il.com>
Date: Wed, 15 Mar 2017 10:39:12 -0700

> This patch series lays the groundwork for future work to allow us to make
> full use of the mqprio options when offloading them to hardware.
> 
> Currently when we specify the hardware offload for mqprio the queue
> configuration is completely ignored and the hardware is only notified of
> the total number of traffic classes.  The problem is this leads to multiple
> issues, one specific issue being you can pass the queue configuration you
> want and it is totally ignored by the hardware.
> 
> What I am planning to do is add support for "hw" values in the
> configuration greater than 1.  So for example we might have one mode of
> mqprio offload that uses 1 and only offloads the TC counts like we
> currently do.  Then we might look at adding an option 2 which would factor
> in the TCs and the queue count information. This way we can select between
> the type of offload we actually want and existing drivers that don't
> support this can just fall back to their legacy configuration.

This looks fine, series applied, thanks Alex.