From: "Wiles, Keith" <keith.wiles@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mbuf:rearrange mbuf to be more mbuf chain friendly
Date: Sat, 25 Jun 2016 15:48:26 +0000 [thread overview]
Message-ID: <E63AC9A5-3318-4E97-9C86-B7E707048B7D@intel.com> (raw)
In-Reply-To: <1466868582-66201-1-git-send-email-keith.wiles@intel.com>
On 6/25/16, 10:29 AM, "dev on behalf of Keith Wiles" <dev-bounces@dpdk.org on behalf of keith.wiles@intel.com> wrote:
>Move the next pointer to the first cacheline of the rte_mbuf structure
>and move the offload values to the second cacheline to give better
>performance to applications using chained mbufs.
>
>Enabled by a configuration option CONFIG_RTE_MBUF_CHAIN_FRIENDLY default
>is set to No.
>
>Signed-off-by: Keith Wiles <keith.wiles@intel.com>
nak thought I had based these on the current master ☹
next prev parent reply other threads:[~2016-06-25 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 15:29 Keith Wiles
2016-06-25 15:48 ` Wiles, Keith [this message]
2016-06-25 15:55 ` [dpdk-dev] [PATCH v2] " Keith Wiles
2016-06-27 8:21 ` Ananyev, Konstantin
2016-06-27 8:27 ` Olivier Matz
2016-06-27 9:05 ` Thomas Monjalon
2016-06-27 13:06 ` Wiles, Keith
2016-06-27 14:30 ` Thomas Monjalon
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=E63AC9A5-3318-4E97-9C86-B7E707048B7D@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.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).