From: Eric Miao <eric.y.miao@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-netdev <netdev@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 6/8] pxa: make lubbock to use smc91x platform data
Date: Fri, 20 Jun 2008 09:23:07 +0800 [thread overview]
Message-ID: <485B067B.1080207@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806191243400.2982@xanadu.home>
Nicolas Pitre wrote:
> On Thu, 19 Jun 2008, Eric Miao wrote:
>
>> Signed-off-by: Eric Miao <eric.miao@marvell.com>
>
> This (and 7/8 and 8/8) are a bit unfortunate. Maybe not as visible on
> Lubbock which has a SMC91C94 which can do 10mbps only, but the others
> will have poorer performances because of those patches. Did you compare
> performances, let's say with netperf, before and after those patches are
> applied?
>
> I understand your goal of wanting to have a single kernel image that
> dynamically can select the right bus access method for all the concerned
> platforms. But I think you'll see that the runtime overhead has a
> significant impact on network throughput and CPU usage.
>
> I think that some other solution should be explored such that when only
> one machine type (or machine types with the same bus config) is
> configured then the compile time optimizations should remain. Something
> based on the machine_is_lubbock(), machine_is_Mainstone(), and so on,
> which becomes constants with the right kernel configuration.
>
OK, I know your concern. Let's see if we can work this out in another way.
>
> Nicolas
prev parent reply other threads:[~2008-06-20 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 11:08 [PATCH 6/8] pxa: make lubbock to use smc91x platform data Eric Miao
2008-06-19 16:53 ` Nicolas Pitre
2008-06-20 1:23 ` Eric Miao [this message]
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=485B067B.1080207@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nico@cam.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;
as well as URLs for NNTP newsgroup(s).