From: "Nambiar, Amritha" <amritha.nambiar@intel.com>
To: Richard Cochran <richardcochran@gmail.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: intel-wired-lan@lists.osuosl.org,
Or Gerlitz <gerlitz.or@gmail.com>,
alexander.h.duyck@intel.com, kiran.patil@intel.com,
sridhar.samudrala@intel.com, mitch.a.williams@intel.com,
neerav.parikh@intel.com, netdev@vger.kernel.org,
John Fastabend <john.fastabend@gmail.com>,
"Wyborny, Carolyn" <carolyn.wyborny@intel.com>
Subject: Re: [PATCH 0/4] Configuring traffic classes via new hardware offload mechanism in tc/mqprio
Date: Wed, 26 Jul 2017 11:18:30 -0700 [thread overview]
Message-ID: <d1b736ac-6f6c-0aa5-b76c-0192b054ecaa@intel.com> (raw)
In-Reply-To: <20170721094244.nkkmvb7fvk6akbvq@localhost.localdomain>
On 7/21/2017 2:42 AM, Richard Cochran wrote:
> On Mon, May 22, 2017 at 12:31:12PM -0700, Jeff Kirsher wrote:
>> On Fri, 2017-05-19 at 17:58 -0700, Amritha Nambiar wrote:
>>> The following series introduces a new harware offload mode in tc/mqprio
>>> where the TCs, the queue configurations and bandwidth rate limits are
>>> offloaded to the hardware.
>
> ...
>
>> This was meant to be sent out as an RFC, but apparently that did not get
>> conveyed when these were sent out Friday.
>
> I am looking at tc/mqprio and dcb with the purpose of implementing
>
> - Forwarding and Queuing Enhancements for Time-Sensitive Streams (FQTSS)
> 802.1Q-2014 Clause 34
>
> - Scheduled Traffic (time based scheduling)
> P802.1Qbv
>
> using the HW capabilities of the i210. This series looks like a
> promising avenue for these features.
>
> My question is, did series go anywhere?
>
> I didn't see any follow ups on netdev, but maybe I missed something.
I have submitted another series as non-RFC for next-queue maintained by
Jeff Kirsher. This is going to come through the next-queue tree. You can
follow the new series "[PATCH 0/6] Configuring traffic classes via new
hardware offload mechanism in tc/mqprio" at
https://www.mail-archive.com/netdev@vger.kernel.org/msg177390.html
>
> Thanks,
> Richard
>
>
>
prev parent reply other threads:[~2017-07-26 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 0:58 [PATCH 0/4] Configuring traffic classes via new hardware offload mechanism in tc/mqprio Amritha Nambiar
2017-05-19 22:30 ` [Intel-wired-lan] " John Fastabend
2017-05-20 0:58 ` [PATCH 1/4] [next-queue]net: mqprio: Introduce new hardware offload mode in mqprio for offloading full TC configurations Amritha Nambiar
2017-05-24 21:59 ` [Intel-wired-lan] " Alexander Duyck
2017-05-20 0:58 ` [PATCH 2/4] [next-queue]net: i40e: Add infrastructure for queue channel support with the TCs and queue configurations offloaded via mqprio scheduler Amritha Nambiar
2017-05-24 21:45 ` [Intel-wired-lan] " Alexander Duyck
2017-05-20 0:58 ` [PATCH 3/4] [next-queue]net: i40e: Enable mqprio full offload mode in the i40e driver for configuring TCs and queue mapping Amritha Nambiar
2017-05-24 22:05 ` [Intel-wired-lan] " Alexander Duyck
2017-05-20 0:58 ` [PATCH 4/4] [next-queue]net: i40e: Add support to set max bandwidth rates for TCs offloaded via tc/mqprio Amritha Nambiar
2017-05-20 21:15 ` [PATCH 0/4] Configuring traffic classes via new hardware offload mechanism in tc/mqprio Or Gerlitz
2017-05-21 22:35 ` [Intel-wired-lan] " Alexander Duyck
2017-05-22 3:25 ` Or Gerlitz
2017-05-22 16:40 ` Duyck, Alexander H
2017-05-22 19:31 ` Jeff Kirsher
2017-07-21 9:42 ` Richard Cochran
2017-07-26 18:18 ` Nambiar, Amritha [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1b736ac-6f6c-0aa5-b76c-0192b054ecaa@intel.com \
--to=amritha.nambiar@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=gerlitz.or@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kiran.patil@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=neerav.parikh@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sridhar.samudrala@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).