From: Edward Cree <ecree@solarflare.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>, netdev <netdev@vger.kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Cong Wang <xiyou.wangcong@gmail.com>,
"Or Gerlitz" <gerlitz.or@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"PJ Waskiewicz" <pjwaskiewicz@gmail.com>,
Anjali Singhai Jain <anjali.singhai@intel.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: TC stats / hw offload question
Date: Mon, 18 Feb 2019 19:37:06 +0000 [thread overview]
Message-ID: <e0ff891b-5e6a-2413-9795-e1e97b7c9048@solarflare.com> (raw)
In-Reply-To: <5930f8e7-3615-5470-ea09-f0e6f2a3a3d7@solarflare.com>
On 18/02/19 18:56, Edward Cree wrote:
> (or
> maybe require it to be set to some distinguished value, like 0, to
> mean 'allocate', so that as a future extension we can support
> shareable counters).
Turns out 0 isn't an option, because TC already internally swallows
that and allocates its own index (same as if 'index' wasn't specified
on cmdline at all), unless we can change TC to pass that 0 on to the
driver.
-Ed
next prev parent reply other threads:[~2019-02-18 19:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 19:41 TC stats / hw offload question Edward Cree
2019-02-06 2:20 ` Jamal Hadi Salim
2019-02-08 10:26 ` Edward Cree
2019-02-09 17:39 ` Jamal Hadi Salim
2019-02-11 11:44 ` Edward Cree
2019-02-14 12:39 ` Jamal Hadi Salim
2019-02-14 15:17 ` Andy Gospodarek
2019-02-18 18:56 ` Edward Cree
2019-02-18 19:37 ` Edward Cree [this message]
2019-04-24 14:05 ` Edward Cree
2019-04-24 14:11 ` Pablo Neira Ayuso
2019-04-24 15:03 ` Edward Cree
2019-04-25 13:23 ` Edward Cree
2019-04-25 22:33 ` Pablo Neira Ayuso
2019-04-26 12:13 ` Edward Cree
2019-04-26 12:42 ` Jamal Hadi Salim
2019-04-26 18:49 ` Pablo Neira Ayuso
2019-04-29 14:11 ` Edward Cree
2019-04-29 15:21 ` Pablo Neira Ayuso
2019-04-29 16:25 ` Edward Cree
2019-04-29 19:14 ` Pablo Neira Ayuso
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=e0ff891b-5e6a-2413-9795-e1e97b7c9048@solarflare.com \
--to=ecree@solarflare.com \
--cc=andy@greyhouse.net \
--cc=anjali.singhai@intel.com \
--cc=gerlitz.or@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pjwaskiewicz@gmail.com \
--cc=xiyou.wangcong@gmail.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