Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2 2/8] taprio: Add support for frame preemption offload
Date: Thu, 21 Jan 2021 15:17:14 -0800	[thread overview]
Message-ID: <878s8lyj5x.fsf@vcostago-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <20210119182133.038fbfc3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

Jakub Kicinski <kuba@kernel.org> writes:

> On Mon, 18 Jan 2021 16:40:22 -0800 Vinicius Costa Gomes wrote:
>> Adds a way to configure which traffic classes are marked as
>> preemptible and which are marked as express.
>> 
>> Even if frame preemption is not a "real" offload, because it can't be
>> executed purely in software, having this information near where the
>> mapping of traffic classes to queues is specified, makes it,
>> hopefully, easier to use.
>> 
>> taprio will receive the information of which traffic classes are
>> marked as express/preemptible, and when offloading frame preemption to
>> the driver will convert the information, so the driver receives which
>> queues are marked as express/preemptible.
>> 
>> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>
>> @@ -1286,13 +1289,15 @@ static int taprio_disable_offload(struct net_device *dev,
>>  	offload->enable = 0;
>>  
>>  	err = ops->ndo_setup_tc(dev, TC_SETUP_QDISC_TAPRIO, offload);
>> -	if (err < 0) {
>> +	if (err < 0)
>> +		NL_SET_ERR_MSG(extack,
>> +			       "Device failed to disable offload");
>> +
>> +	err = ops->ndo_setup_tc(dev, TC_SETUP_PREEMPT, &preempt);
>> +	if (err < 0)
>>  		NL_SET_ERR_MSG(extack,
>>  			       "Device failed to disable offload");
>
> This was meant to say something else?

Yeah, better to say which offload failed to be disabled. Will fix.


Cheers,
-- 
Vinicius

  reply	other threads:[~2021-01-21 23:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  0:40 [Intel-wired-lan] [PATCH net-next v2 0/8] ethtool: Add support for frame preemption Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 1/8] ethtool: Add support for configuring " Vinicius Costa Gomes
2021-01-19  0:52   ` Vladimir Oltean
2021-01-19 23:03     ` Vinicius Costa Gomes
2021-01-20  2:17   ` Jakub Kicinski
2021-01-21 23:18     ` Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 2/8] taprio: Add support for frame preemption offload Vinicius Costa Gomes
2021-01-20  2:21   ` Jakub Kicinski
2021-01-21 23:17     ` Vinicius Costa Gomes [this message]
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 3/8] igc: Set the RX packet buffer size for TSN mode Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 4/8] igc: Only dump registers if configured to dump HW information Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 5/8] igc: Avoid TX Hangs because long cycles Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 6/8] igc: Add support for tuning frame preemption via ethtool Vinicius Costa Gomes
2021-01-20  2:23   ` Jakub Kicinski
2021-01-21 23:18     ` Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 7/8] igc: Add support for Frame Preemption offload Vinicius Costa Gomes
2021-01-19  0:40 ` [Intel-wired-lan] [PATCH net-next v2 8/8] igc: Separate TSN configurations that can be updated Vinicius Costa Gomes

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=878s8lyj5x.fsf@vcostago-mobl2.amr.corp.intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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