From: Ido Schimmel <idosch@idosch.org>
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
dsahern@kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH net-next v3] ipv6: ioam: Support for Queue depth data field
Date: Thu, 30 Dec 2021 21:18:19 +0200 [thread overview]
Message-ID: <Yc4F+w447cs1SBuD@shredder> (raw)
In-Reply-To: <20211230171004.16368-1-justin.iurman@uliege.be>
On Thu, Dec 30, 2021 at 06:10:04PM +0100, Justin Iurman wrote:
> v3:
> - Report 'backlog' (bytes) instead of 'qlen' (number of packets)
>
> v2:
> - Fix sparse warning (use rcu_dereference)
>
> This patch adds support for the queue depth in IOAM trace data fields.
>
> The draft [1] says the following:
>
> The "queue depth" field is a 4-octet unsigned integer field. This
> field indicates the current length of the egress interface queue of
> the interface from where the packet is forwarded out. The queue
> depth is expressed as the current amount of memory buffers used by
> the queue (a packet could consume one or more memory buffers,
> depending on its size).
>
> An existing function (i.e., qdisc_qstats_qlen_backlog) is used to
> retrieve the current queue length without reinventing the wheel.
>
> Note: it was tested and qlen is increasing when an artificial delay is
> added on the egress with tc.
>
> [1] https://datatracker.ietf.org/doc/html/draft-ietf-ippm-ioam-data#section-5.4.2.7
>
> Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2021-12-30 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 17:10 [PATCH net-next v3] ipv6: ioam: Support for Queue depth data field Justin Iurman
2021-12-30 19:18 ` Ido Schimmel [this message]
2022-01-02 12:20 ` patchwork-bot+netdevbpf
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=Yc4F+w447cs1SBuD@shredder \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).