From: Vijay Nikam <vijay.t.nikam@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [gianfar]bandwidth management problem on mpc8313 based board
Date: Wed, 8 Jun 2011 16:21:03 +0530 [thread overview]
Message-ID: <BANLkTino1HgB2SL=S6ZeZ-z3o1MczWJ+8w@mail.gmail.com> (raw)
In-Reply-To: <20110607142213.2851f92e@schlenkerla.am.freescale.net>
Hello Scott,
Thanks for the prompt reply.
> What's your CPU utilization? The CPU may just not be able to keep up wit=
h
> that much traffic, with the software you're running.
The software I am using to check bandwidth is 'iperf'. Without running iper=
f the
CPU utilization varies around 30-50% and with iperf running it shoots
upto 99.9%.
> What packet size are you using?
The packet size is - 1518 + VLAN_Tag (4Bytes) =3D 1522 Bytes
Another point which I would like to clear is that mpc8313 has eth0 (eTsec1)=
of
1Gbps, if more than 50% of CPU Time is available then why the total bandwid=
th
should limit to less than 100 Mbps? At least 400Mbps should be expected, p=
lease
correct if I am wrong!
Please acknowledge, thanks.
Kind Regards,
Vijay Nikam
On Wed, Jun 8, 2011 at 12:52 AM, Scott Wood <scottwood@freescale.com> wrote=
:
> On Tue, 7 Jun 2011 18:32:37 +0530
> Vijay Nikam <vijay.t.nikam@gmail.com> wrote:
>
>> Dear All,
>>
>> I have mpc8313 powerpc based board with silicon revision 2.1. the
>> processor has two ETH ports (eTsec1 and eTsec2) i.e. eth0 and eth1.
>> eth0 is 1Gbps port and eth1 is 100Mbps port. On board there is L2
>> switch from TANTOS2G (psb6972) supports one port 1Gbps,
>> and from switch there are 4 more eth ports derived which are 100Mbps
>> ports and port based VLAN is configured for this purpose.
>>
>> The interface between switch and eth0 (port of processor) is RGMII. So
>> the processor port and switch port are connected on 1Gbps Link.
>> The other 4 derived ports (100Mbps) are used to connect to external worl=
d.
>> On this board Embedded Linux is running of kernel version 2.6.23 with HR=
T patch.
>
> That's rather old.
>
>> The ethernet controller driver in use is "gianfar" version 1.3
>> The driver is configured properly as it determines both links 1000Mbps
>> (eth0) and 100Mbps (eth1) also verified with ethtool.
>>
>> After this I started to perform bandwidth test using iperf tool.
>> When I performed this test on one port out of 4 derived ports I am
>> getting bandwidth in the range of 80-85Mbps
>> but when the same test is performed on 2 ports simultaneously then the
>> per port bandwidth is reduced to 40-45Mbps.
>>
>> But my understanding is all of the 4 ports should support 100Mbps
>> bandwidth simultaneously (as base port is 1Gbps).
>> Then why bandwidth gets reduced when more than one port are
>> communicating simultaneously?
>> Any reason or suggestion I should check for this problem?
>
> What's your CPU utilization? =A0The CPU may just not be able to keep up w=
ith
> that much traffic, with the software you're running.
>
> What packet size are you using?
>
> -Scott
>
>
next prev parent reply other threads:[~2011-06-08 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 13:02 [gianfar]bandwidth management problem on mpc8313 based board Vijay Nikam
2011-06-07 19:22 ` Scott Wood
2011-06-08 10:51 ` Vijay Nikam [this message]
2011-06-08 17:00 ` Scott Wood
2011-06-08 11:25 ` David Laight
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='BANLkTino1HgB2SL=S6ZeZ-z3o1MczWJ+8w@mail.gmail.com' \
--to=vijay.t.nikam@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 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).