public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] net: hisilicon: new hip04 ethernet driver
Date: Thu, 03 Apr 2014 10:35:11 +0200	[thread overview]
Message-ID: <7201300.YltrNpx6X5@wuerfel> (raw)
In-Reply-To: <CAMj5BkgfwE1hHpVeqH9WRitwCB30x3c4w0qw7sXT3PiOV-QcPQ@mail.gmail.com>

On Thursday 03 April 2014 14:24:25 Zhangfei Gao wrote:
> On Wed, Apr 2, 2014 at 11:49 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Wednesday 02 April 2014 10:04:34 David Laight wrote:
> >> What you need to avoid is reads from uncached memory.
> >> It may well beneficial for the tx reclaim code to first
> >> check whether all the transmits have completed (likely)
> >> instead of testing each descriptor in turn.
> >
> > Good point, reading from noncached memory is actually the
> > part that matters. For slow networks (e.g. 10mbit), checking if
> > all of the descriptors have finished is not quite as likely to succeed
> > as for fast (gbit), especially if the timeout is set to expire
> > before all descriptors have completed.
> >
> > If it makes a lot of difference to performance, one could use
> > a binary search over the outstanding descriptors rather than looking
> > just at the last one.
> >
> 
> I am afraid, there may no simple way to check whether all transmits completed.

Why can't you do the trivial change that David suggested above? It
sounds like a three line change to your current code. No need to do
the binary change at first, just see what difference it makes.

> Still want enable the cache coherent feature first.
> Then two benefits:
> 1. dma buffer cacheable.
> 2. descriptor can directly use cacheable memory, so the performance
> concern here may be solved accordingly.
> 
> So how about using this version as first version, while tuning the
> performance in the next step.
> Currently, the gbit interface can reach 420M bits/s in iperf, and the
> 100M interface can reach 94M bits/s.

It sounds like a very simple thing to try and you'd know immediately
if it helps or not.

Besides, you still have to change the other two issues I mentioned
regarding the tx reclaim, so you can do all three at once.

	Arnd

  reply	other threads:[~2014-04-03  8:35 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 13:27 [PATCH v5 0/3] add hisilicon hip04 ethernet driver Zhangfei Gao
2014-04-01 13:27 ` [PATCH 1/3] Documentation: add Device tree bindings for Hisilicon hip04 ethernet Zhangfei Gao
2014-04-01 13:27 ` [PATCH 2/3] net: hisilicon: new hip04 MDIO driver Zhangfei Gao
2014-04-04 15:42   ` Zhangfei Gao
2014-04-04 17:48     ` David Miller
2014-04-01 13:27 ` [PATCH 3/3] net: hisilicon: new hip04 ethernet driver Zhangfei Gao
2014-04-02  9:21   ` Arnd Bergmann
2014-04-02  9:51     ` zhangfei
2014-04-02 15:24       ` Arnd Bergmann
2014-04-02 10:04     ` David Laight
2014-04-02 15:49       ` Arnd Bergmann
2014-04-03  6:24         ` Zhangfei Gao
2014-04-03  8:35           ` Arnd Bergmann [this message]
2014-04-03 15:22       ` David Miller
2014-04-03 15:38       ` zhangfei
2014-04-03 15:27     ` Russell King - ARM Linux
2014-04-03 15:42       ` David Laight
2014-04-03 15:50         ` Russell King - ARM Linux
2014-04-03 17:57       ` Arnd Bergmann
2014-04-04  6:52       ` Zhangfei Gao
  -- strict thread matches above, loose matches on Subject: below --
2014-04-05  4:35 [PATCH v7 0/3] add hisilicon " Zhangfei Gao
2014-04-05  4:35 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-04-07 18:53   ` David Miller
2014-04-08  8:07     ` zhangfei
2014-04-08  8:30       ` David Laight
2014-04-08  9:42         ` Arnd Bergmann
2014-04-08 14:47         ` zhangfei
2014-04-18 13:17     ` zhangfei
2014-04-07 18:56   ` David Miller
2014-04-04 15:16 [PATCH v6 0/3] add hisilicon " Zhangfei Gao
2014-04-04 15:16 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-03-28 15:35 [PATCH v4 0/3] add hisilicon " Zhangfei Gao
2014-03-28 15:36 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-03-24 14:14 [PATCH v3 0/3] add hisilicon " Zhangfei Gao
2014-03-24 14:14 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-03-24 15:18   ` Arnd Bergmann
2014-03-25  4:06     ` Zhangfei Gao
2014-03-25  8:12       ` Arnd Bergmann
2014-03-25 17:00         ` Florian Fainelli
2014-03-25 17:05           ` Arnd Bergmann
2014-03-25 17:16             ` Florian Fainelli
2014-03-25 17:57               ` Arnd Bergmann
2014-03-26  9:55                 ` David Laight
2014-03-25 17:17             ` David Laight
2014-03-25 17:21             ` Eric Dumazet
2014-03-25 17:54               ` Arnd Bergmann
2014-03-27 12:53                 ` zhangfei
2014-03-24 16:32   ` Florian Fainelli
2014-03-24 17:23     ` Arnd Bergmann
2014-03-24 17:35       ` Florian Fainelli
2014-03-27  6:27     ` Zhangfei Gao
2014-03-21 15:09 [PATCH v2 0/3] add hisilicon " Zhangfei Gao
2014-03-21 15:09 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-03-21 15:27   ` Arnd Bergmann
2014-03-22  1:18     ` zhangfei
2014-03-22  8:08       ` Arnd Bergmann
2014-03-18  8:40 [PATCH 0/3] add hisilicon " Zhangfei Gao
2014-03-18  8:40 ` [PATCH 3/3] net: hisilicon: new " Zhangfei Gao
2014-03-18 10:46   ` Russell King - ARM Linux
2014-03-20  9:51     ` Zhangfei Gao
2014-03-24 14:17       ` Rob Herring
2014-03-26 14:22         ` Zhangfei Gao
2014-03-18 11:25   ` Arnd Bergmann
2014-03-20 14:00     ` Zhangfei Gao
2014-03-20 14:31       ` Arnd Bergmann
2014-03-21  5:19         ` Zhangfei Gao
2014-03-21  7:37           ` Arnd Bergmann
2014-03-21  7:56             ` Zhangfei Gao
2014-03-24  8:17         ` Zhangfei Gao
2014-03-24 10:02           ` Arnd Bergmann
2014-03-24 13:23             ` Zhangfei Gao

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=7201300.YltrNpx6X5@wuerfel \
    --to=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox