From: Justin Iurman <justin.iurman@uliege.be>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, dsahern@kernel.org,
yoshfuji@linux-ipv6.org, linux-mm@kvack.org, cl@linux.com,
penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, vbabka@suse.cz,
justin.iurman@uliege.be
Subject: [RFC net-next 0/2] IOAM queue depth and buffer occupancy
Date: Mon, 6 Dec 2021 22:17:56 +0100 [thread overview]
Message-ID: <20211206211758.19057-1-justin.iurman@uliege.be> (raw)
Request for comments on this solution to add support for two IOAM trace
data fields, i.e., queue depth and buffer occupancy. CC'ing mm people
for patch #2. See commit messages for more details.
Justin Iurman (2):
ipv6: ioam: Support for Queue depth data field
ipv6: ioam: Support for Buffer occupancy data field
include/linux/slab.h | 15 +++++++++++++++
mm/slab.h | 14 --------------
net/ipv6/ioam6.c | 27 +++++++++++++++++++++++++--
3 files changed, 40 insertions(+), 16 deletions(-)
--
2.25.1
next reply other threads:[~2021-12-06 21:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 21:17 Justin Iurman [this message]
2021-12-06 21:17 ` [RFC net-next 1/2] ipv6: ioam: Support for Queue depth data field Justin Iurman
2021-12-06 21:17 ` [RFC net-next 2/2] ipv6: ioam: Support for Buffer occupancy " Justin Iurman
2021-12-07 0:16 ` Jakub Kicinski
2021-12-07 11:54 ` Justin Iurman
2021-12-07 15:50 ` Jakub Kicinski
2021-12-07 16:35 ` Justin Iurman
2021-12-07 17:07 ` Jakub Kicinski
2021-12-07 18:05 ` Justin Iurman
2021-12-08 22:18 ` Jakub Kicinski
2021-12-09 14:10 ` Justin Iurman
2021-12-10 0:38 ` Jakub Kicinski
2021-12-10 12:57 ` Justin Iurman
2021-12-21 17:06 ` Justin Iurman
2021-12-21 17:23 ` Vladimir Oltean
2021-12-21 20:13 ` Jakub Kicinski
2021-12-22 16:13 ` Justin Iurman
2021-12-22 15:49 ` Justin Iurman
2021-12-07 16:37 ` David Ahern
2021-12-07 16:54 ` Justin Iurman
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=20211206211758.19057-1-justin.iurman@uliege.be \
--to=justin.iurman@uliege.be \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--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 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.