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, 11 Feb 2019 11:44:35 +0000 [thread overview]
Message-ID: <11ab2dc0-ec39-18cd-d170-0d5f954198b9@solarflare.com> (raw)
In-Reply-To: <561205a6-101b-c86b-e77d-6ebdcf31a56d@mojatatu.com>
On 09/02/19 17:39, Jamal Hadi Salim wrote:
> On 2019-02-08 5:26 a.m., Edward Cree wrote:
>> I can't find any stats counters on
>> the "match" either in the software path or the offload API.
>
> Hasnt been necessary thus far.
> Is your end goal to match and count?
My end goal is to implement TC offload in some hw we're designing
here at Solarflare. So I'm trying to determine what hardware is
expected/required to do.
It might be possible to design our new hw so that we can attach a
counter to every action, if that's what TC wants. But since the
other vendors don't seem to do that, I wondered if there was a
reason, or if perhaps the counter resources (and PCI bw to read
them) could be saved if all those separate counters aren't really
needed. Right now the design we are considering would only count
packets as-matched, i.e. before any edits. That's fine for encap
— you can calculate the bytes correction in SW — but not for decap
since in principle the length of the RXed outer headers could
vary (e.g. you might have IP options there).
-Ed
next prev parent reply other threads:[~2019-02-11 11:44 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 [this message]
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
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=11ab2dc0-ec39-18cd-d170-0d5f954198b9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.