All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Du, Fan" <fan.du@intel.com>
To: "Yankejian (Hackim Yim)" <yankejian@huawei.com>,
	davem@davemloft.net, lisheng011@huawei.com, lipeng321@huawei.com,
	salil.mehta@huawei.com, huangdaode@hisilicon.com,
	xuwei5@hisilicon.com, liguozhu@huawei.com
Cc: haifeng.wei@huawei.com, yisen.zhuang@huawei.com,
	linuxarm@huawei.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: hns: optimize XGE capability by reducing cpu usage
Date: Tue, 08 Dec 2015 14:30:57 +0800	[thread overview]
Message-ID: <56667921.2010006@intel.com> (raw)
In-Reply-To: <56667729.1080701@huawei.com>



On 2015/12/8 14:22, Yankejian (Hackim Yim) wrote:
>
> On 2015/12/7 16:58, Du, Fan wrote:
>> >
>> >
>> >On 2015/12/5 15:32, yankejian wrote:
>>> >>here is the patch raising the performance of XGE by:
>>> >>1)changes the way page management method for enet momery, and
>>> >>2)reduces the count of rmb, and
>>> >>3)adds Memory prefetching
>> >
>> >Any numbers on how much it boost performance?
>> >
> it is almost the same as 82599.

I mean how much it improves performance *BEFORE* and *AFTER* this patch
for Huawei XGE chip, because the commit log states it "raising the 
performance",
but did give numbers of the testing.

  reply	other threads:[~2015-12-08  6:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05  7:32 [PATCH net-next] net: hns: optimize XGE capability by reducing cpu usage yankejian
2015-12-07  3:29 ` David Miller
2015-12-07  3:32   ` Joe Perches
2015-12-07  8:58     ` Yankejian (Hackim Yim)
2015-12-07  9:05       ` Joe Perches
2015-12-07  9:26         ` Yankejian (Hackim Yim)
2015-12-07  8:37   ` Yankejian (Hackim Yim)
2015-12-07  8:58 ` Du, Fan
2015-12-08  6:22   ` Yankejian (Hackim Yim)
2015-12-08  6:30     ` Du, Fan [this message]
2015-12-08  6:58       ` Yankejian (Hackim Yim)

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=56667921.2010006@intel.com \
    --to=fan.du@intel.com \
    --cc=davem@davemloft.net \
    --cc=haifeng.wei@huawei.com \
    --cc=huangdaode@hisilicon.com \
    --cc=liguozhu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lipeng321@huawei.com \
    --cc=lisheng011@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=xuwei5@hisilicon.com \
    --cc=yankejian@huawei.com \
    --cc=yisen.zhuang@huawei.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.