All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Randy Tice (rtice)" <rtice@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
	"Harman Kalra" <hkalra@marvell.com>
Subject: Re: [PATCH v4 0/1] mbuf: add runtime metadata dynamic-field storage
Date: Fri, 9 Oct 2026 12:16:03 -0700	[thread overview]
Message-ID: <20261009121603.1f97aca8@phoenix.local> (raw)
In-Reply-To: <PH0PR11MB76165F045BA8ECE8877446B9A9922@PH0PR11MB7616.namprd11.prod.outlook.com>

On Fri, 9 Oct 2026 18:12:20 +0000
"Randy Tice (rtice)" <rtice@cisco.com> wrote:

> Stephen,
> I’m thinking, perhaps the best path forward for now, is to continue using a private mbuf layout and carry the collateral internally — at least for now. The changes are getting well beyond the initial desired impacts and has potential make things become unstable.
> 
> I would love to see some sort of solution along these lines in the future so we can discontinue the use of a private patch. To be clear, the solution is not built around cnxk, cnxk is just impacted — we have several other platform builds that do not use cnxk but we still carry the metadata in the mbuf itself for performance reasons.
> 
> WRT the skip functions, we fit under the 384 max for wqe but there’s no room for additional growth beyond that with how it’s laid out. The other 2 are not as sensitive to the size but still have valid limits which are well beyond our use case. Today we carry 256 bytes which caps us on wqe.
> 
> That said, we plan to discuss internally next week on how to move forward as we prep for our v25.11 upgrade work. I want to thank you and Morten, however, for your time and support on this work.
> Regards,
> -rt

I do think CNXK needs fixing.

      reply	other threads:[~2026-10-09 19:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 19:37 [PATCH 0/1] mbuf: add optional dynfield3 storage Randy L Tice
2026-09-24 19:37 ` [PATCH 1/1] " Randy L Tice
2026-09-25  9:48   ` Morten Brørup
2026-09-25 19:31 ` [PATCH v2 0/1] " Randy L Tice
2026-09-25 19:31   ` [PATCH v2 1/1] " Randy L Tice
2026-09-26 16:51     ` Stephen Hemminger
2026-09-28 14:45       ` Randy Tice (rtice)
2026-09-28 18:16   ` [PATCH v3 0/1] mbuf: add optional no-copy dynamic field storage Randy L Tice
2026-09-28 18:16     ` [PATCH v3 1/1] " Randy L Tice
2026-09-29  7:15       ` Morten Brørup
2026-09-29 11:59       ` Konstantin Ananyev
2026-09-29 12:44         ` Morten Brørup
2026-09-29 13:12           ` Konstantin Ananyev
2026-09-29 13:34             ` Morten Brørup
2026-09-29 14:14               ` Konstantin Ananyev
2026-09-29 14:44                 ` Randy Tice (rtice)
2026-09-29 15:20                   ` Morten Brørup
2026-09-29 19:03                     ` Randy Tice (rtice)
2026-09-29 19:28                       ` Konstantin Ananyev
2026-09-29 19:26                   ` Konstantin Ananyev
2026-10-06 15:54     ` [PATCH v4 0/1] mbuf: add runtime metadata dynamic-field storage Randy L Tice
2026-10-06 15:54       ` [PATCH v4 1/1] " Randy L Tice
2026-10-06 16:51       ` [PATCH v4 0/1] " Stephen Hemminger
2026-10-08 16:15         ` Randy Tice (rtice)
2026-10-09 16:14           ` Stephen Hemminger
2026-10-09 18:12             ` Randy Tice (rtice)
2026-10-09 19:16               ` Stephen Hemminger [this message]

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=20261009121603.1f97aca8@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=mb@smartsharesystems.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rtice@cisco.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.