From: Thomas Monjalon <thomas@monjalon.net>
To: Parthakumar Roy <partha.roy.tx@gmail.com>,
Parthakumar Roy <Parthakumar.Roy@ibm.com>
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v2] build: make buffer headroom configurable
Date: Wed, 06 Mar 2024 17:45:40 +0100 [thread overview]
Message-ID: <3845446.FjKLVJYuhi@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F27A@smartserver.smartshare.dk>
27/02/2024 17:10, Morten Brørup:
> > From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> > Sent: Tuesday, 27 February 2024 17.02
> >
> > While this is not likely a setting that many will need to change, it's
> > not
> > the first time I've heard of users looking to adjust it.
> >
> > Because it's such a simple change, I'd support having this accessible
> > for
> > easy config by end-users.
> >
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> +1 to what Bruce said.
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
Changed the definition to something shorter:
"Default data offset (in bytes) in a packet buffer to leave room for additional headers."
Applied, thanks.
next prev parent reply other threads:[~2024-03-06 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 19:02 meson option to customize RTE_PKTMBUF_HEADROOM patch Parthakumar Roy
2024-02-16 7:52 ` David Marchand
2024-02-20 14:57 ` [PATCH v2] build: make buffer headroom configurable Parthakumar Roy
2024-02-27 16:02 ` Bruce Richardson
2024-02-27 16:10 ` Morten Brørup
2024-03-06 16:45 ` Thomas Monjalon [this message]
2024-03-23 20:51 ` meson option to customize RTE_PKTMBUF_HEADROOM patch Garrett D'Amore
2024-03-25 10:01 ` Bruce Richardson
2024-03-25 17:20 ` Stephen Hemminger
2024-03-25 22:56 ` Garrett D'Amore
2024-03-26 8:05 ` Morten Brørup
2024-03-26 14:19 ` Garrett D'Amore
2024-03-26 15:06 ` Morten Brørup
2024-03-26 17:43 ` Garrett D'Amore
2024-03-26 20:35 ` Stephen Hemminger
2024-03-26 21:10 ` Garrett D'Amore
2024-03-26 16:14 ` Konstantin Ananyev
2024-03-26 17:44 ` Garrett D'Amore
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=3845446.FjKLVJYuhi@thomas \
--to=thomas@monjalon.net \
--cc=Parthakumar.Roy@ibm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=partha.roy.tx@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.