From: Justin Iurman <justin.iurman@uliege.be>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
yoshfuji@linux-ipv6.org, linux-mm@kvack.org, cl@linux.com,
penberg@kernel.org, rientjes@google.com,
iamjoonsoo kim <iamjoonsoo.kim@lge.com>,
akpm@linux-foundation.org, vbabka@suse.cz,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>,
Andrew Lunn <andrew@lunn.ch>,
Stephen Hemminger <sthemmin@microsoft.com>,
Vladimir Oltean <olteanv@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Florian Westphal <fw@strlen.de>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [RFC net-next 2/2] ipv6: ioam: Support for Buffer occupancy data field
Date: Fri, 10 Dec 2021 13:57:12 +0100 (CET) [thread overview]
Message-ID: <1887416432.225095145.1639141032334.JavaMail.zimbra@uliege.be> (raw)
In-Reply-To: <20211209163828.223815bd@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
>> Indeed, would be a better fit. I didn't know about this one, thanks for
>> that. It's a shame it can't be used in this context, though. But, at the
>> end of the day, we're left with nothing regarding buffer occupancy. So
>> I'm wondering if "something" is not better than "nothing" in this case.
>> And, for that, we're back to my previous answer on why I agree and
>> disagree with what you said about its utility.
>
> I think we're on the same page, the main problem is I've not seen
> anyone use the skbuff_head_cache occupancy as a signal in practice.
Indeed.
> I'm adding a bunch of people to the CC list, hopefully someone has
> an opinion one way or the other.
+1, thanks Jakub.
> Lore link to the full thread, FWIW:
>
> https://lore.kernel.org/all/20211206211758.19057-1-justin.iurman@uliege.be/
next prev parent reply other threads:[~2021-12-10 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 21:17 [RFC net-next 0/2] IOAM queue depth and buffer occupancy Justin Iurman
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 [this message]
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=1887416432.225095145.1639141032334.JavaMail.zimbra@uliege.be \
--to=justin.iurman@uliege.be \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roopa@nvidia.com \
--cc=sthemmin@microsoft.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.