From: Stephen Hemminger <shemming@brocade.com>
To: <dev@dpdk.org>, Helin Zhang <helin.zhang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 ] ixgbe: speed up transmit
Date: Fri, 11 Dec 2015 08:48:19 -0800 [thread overview]
Message-ID: <20151211084819.2177795d@xeon-e3> (raw)
In-Reply-To: <1447431013-23245-1-git-send-email-stephen@networkplumber.org>
On Fri, 13 Nov 2015 08:10:13 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> From: Stephen Hemminger <shemming@brocade.com>
>
> The freeing of mbuf's in ixgbe is one of the observable hot spots
> under load. Optimize it by doing bulk free of mbufs using code similar
> to i40e and fm10k.
>
> Drop the no longer needed micro-optimization for the no refcount flag.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
How come this patch got no review or comments?
It gets a visible performance gain of up to 10% in some cases.
I understand maintainers are busy with internal work, but they need
to read mailing list as well.
next prev parent reply other threads:[~2015-12-11 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 16:10 Stephen Hemminger
2015-12-11 16:48 ` Stephen Hemminger [this message]
2015-12-11 18:52 ` Ananyev, Konstantin
2016-02-10 15:19 ` Bruce Richardson
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=20151211084819.2177795d@xeon-e3 \
--to=shemming@brocade.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--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).