From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next v3 0/4] net: mvneta: improve rx/tx performance
Date: Fri, 24 Feb 2017 19:56:48 +0800 [thread overview]
Message-ID: <20170224195648.219d6b50@xhacker> (raw)
In-Reply-To: <20170221.111602.860315087619854954.davem@davemloft.net>
Hi David, Marcin,
On Tue, 21 Feb 2017 11:16:02 -0500 David Miller wrote:
> From: Jisheng Zhang <jszhang@marvell.com>
> Date: Tue, 21 Feb 2017 12:37:40 +0800
>
> > Thanks for your review.
> >
> > The measurement is simple: record how much time we spent in mvneta_rx_swbm()
> > for receiving 1GB data, something as below:
>
> Please use a standard tool for measuring performance, rather than profiling
> the driver and trying to derive numbers that way.
Got your point. I will try to get performance with standard tool and cook a
v4 once rc1 is released.
Thanks,
Jisheng
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: David Miller <davem@davemloft.net>, <mw@semihalf.com>
Cc: <gregory.clement@free-electrons.com>,
<thomas.petazzoni@free-electrons.com>, <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 0/4] net: mvneta: improve rx/tx performance
Date: Fri, 24 Feb 2017 19:56:48 +0800 [thread overview]
Message-ID: <20170224195648.219d6b50@xhacker> (raw)
In-Reply-To: <20170221.111602.860315087619854954.davem@davemloft.net>
Hi David, Marcin,
On Tue, 21 Feb 2017 11:16:02 -0500 David Miller wrote:
> From: Jisheng Zhang <jszhang@marvell.com>
> Date: Tue, 21 Feb 2017 12:37:40 +0800
>
> > Thanks for your review.
> >
> > The measurement is simple: record how much time we spent in mvneta_rx_swbm()
> > for receiving 1GB data, something as below:
>
> Please use a standard tool for measuring performance, rather than profiling
> the driver and trying to derive numbers that way.
Got your point. I will try to get performance with standard tool and cook a
v4 once rc1 is released.
Thanks,
Jisheng
next prev parent reply other threads:[~2017-02-24 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 12:53 [PATCH net-next v3 0/4] net: mvneta: improve rx/tx performance Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 12:53 ` [PATCH net-next v3 1/4] net: mvneta: avoid getting status from rx_desc as much as possible Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 12:53 ` [PATCH net-next v3 2/4] net: mvneta: avoid getting buf_phys_addr from rx_desc again Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 12:53 ` [PATCH net-next v3 3/4] net: mvneta: avoid reading from tx_desc as much as possible Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 12:53 ` [PATCH net-next v3 4/4] net: mvneta: Use cacheable memory to store the rx buffer DMA address Jisheng Zhang
2017-02-20 12:53 ` Jisheng Zhang
2017-02-20 14:21 ` [PATCH net-next v3 0/4] net: mvneta: improve rx/tx performance Gregory CLEMENT
2017-02-20 14:21 ` Gregory CLEMENT
2017-02-21 4:37 ` Jisheng Zhang
2017-02-21 4:37 ` Jisheng Zhang
2017-02-21 4:37 ` Jisheng Zhang
2017-02-21 16:16 ` David Miller
2017-02-21 16:16 ` David Miller
2017-02-21 16:35 ` Marcin Wojtas
2017-02-21 16:35 ` Marcin Wojtas
2017-02-24 11:56 ` Jisheng Zhang [this message]
2017-02-24 11:56 ` Jisheng Zhang
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=20170224195648.219d6b50@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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 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.