From: Olivier MATZ <olivier.matz@6wind.com>
To: Paul Emmerich <emmericp@net.in.tum.de>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] TX performance regression caused by the mbuf cachline split
Date: Fri, 19 Feb 2016 13:31:32 +0100 [thread overview]
Message-ID: <56C70B24.404@6wind.com> (raw)
In-Reply-To: <56C223CB.9080901@net.in.tum.de>
Hi Paul,
On 02/15/2016 08:15 PM, Paul Emmerich wrote:
> The bulk_alloc patch is great and helps. I'd love to see such a function
> in DPDK.
>
A patch has been submitted by Huawei. I guess it will be integrated
soon.
See http://dpdk.org/dev/patchwork/patch/10122/
Regards,
Olivier
prev parent reply other threads:[~2016-02-19 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 0:14 Paul Emmerich
2015-05-11 9:13 ` Luke Gorrie
2015-05-11 10:16 ` Paul Emmerich
2015-05-11 22:32 ` Paul Emmerich
2015-05-11 23:18 ` Paul Emmerich
2015-05-12 0:28 ` Marc Sune
2015-05-12 0:38 ` Marc Sune
2015-05-13 9:03 ` Ananyev, Konstantin
2016-02-15 19:15 ` Paul Emmerich
2016-02-19 12:31 ` Olivier MATZ [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=56C70B24.404@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=emmericp@net.in.tum.de \
--cc=konstantin.ananyev@intel.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 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).