All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Joao Pinto <Joao.Pinto@synopsys.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next] net: stmmac: add drop transmit status feature
Date: Wed, 12 Apr 2017 15:52:39 +0200	[thread overview]
Message-ID: <20170412135239.GD32596@lunn.ch> (raw)
In-Reply-To: <37cc8294-5514-ed02-9b41-86f8cc9c20ad@synopsys.com>

> >> My setup is FPGA based, so it will have lower performance values.
> >> Iperf results with
> >>   "Drop Transmit Status" set: ~650Mbps.
> >>   "Drop Transmit Status" unset: ~450Mbps.
> > 
> > What percentage of your customers use FPGAs? When i look at the users
> > of this driver, i see ST, Allwinner, Rockchip, Meson, etc. So silicon,
> > not FPGA. Does it make sense to do performance measurements on FPGA,
> > when you say it has lower performance?
> 
> I don't understand your question. Synopsys is an IP vendor, so all recent IPs
> are available for prototyping as you can understand and so early development is
> done using a FPGA.

Sure, early development on FPGA makes sense. But my guess is, > 95% of
the devices running this driver are silicon, not FPGA. The customers
you sell the IP to want to know that the driver is going to work well
on their silicon, not your internal FPGA development setup. The kernel
community want a warm fuzzy feeling that you care about the real
devices out in the wild using this driver. So if you could say, "I
tested on a STM DISCO devel board, and performance went up 20%, an
RK3288 devel board and got 18% performance boost, and a Merrii A80
Optimus Board showed 22% improvements", we would have a lot better
feeling about these patches.

	Andrew

  reply	other threads:[~2017-04-12 13:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:26 [PATCH v2 net-next] net: stmmac: add drop transmit status feature Joao Pinto
2017-04-12 11:56 ` Andrew Lunn
2017-04-12 12:07   ` Joao Pinto
2017-04-12 13:10     ` Andrew Lunn
2017-04-12 13:16       ` Joao Pinto
2017-04-12 13:52         ` Andrew Lunn [this message]
2017-04-12 13:55           ` Joao Pinto
2017-04-12 14:51             ` David Miller
2017-04-12 15:13               ` Joao Pinto
2017-04-12 15:28                 ` David Miller
2017-04-12 15:43                   ` Joao Pinto
2017-04-12 16:03                     ` David Miller
2017-04-12 14:58     ` Andrew Lunn
2017-04-12 17:43       ` Florian Fainelli
2017-04-18 10:25         ` Joao Pinto

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=20170412135239.GD32596@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Joao.Pinto@synopsys.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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.