From: "Michael J. Cohen" <mjc@unre.st>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
bcollins@debian.org, linux1394-devel@lists.sourceforge.net,
linux1394-user@lists.sourceforge.net
Subject: Re: eth1394 performace
Date: Thu, 14 Oct 2004 18:17:19 -0400 [thread overview]
Message-ID: <1097792240.19956.1.camel@localhost> (raw)
In-Reply-To: <1097714485l.6634l.1l@werewolf.able.es>
On Thu, 2004-10-14 at 00:41 +0000, J.A. Magallon wrote:
> Hi all...
>
> I'm trying to link an iBook and my linux box (kernel 2.6.9-rc4-mm1) via FireWire.
> With static IP addresses, it seems to work, but performance is sloow (compared
> to what I expected;):
>
> werewolf:/usr/src/linux# iperf -c ibook
> ------------------------------------------------------------
> Client connecting to ibook, TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.0.1 port 33155 connected with 192.168.0.2 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 110 MBytes 91.8 Mbits/sec
> werewolf:/usr/src/linux# iperf -c ibook-fw
> ------------------------------------------------------------
> Client connecting to ibook-fw, TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.1.1 port 33156 connected with 192.168.1.2 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 90.5 MBytes 75.8 Mbits/sec
Try transferring larger amounts of data. perhaps there is not enough
data to provide a meaningful bandwidth measurement.
HTH,
Michael
prev parent reply other threads:[~2004-10-14 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 0:41 eth1394 performace J.A. Magallon
2004-10-14 22:17 ` Michael J. Cohen [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=1097792240.19956.1.camel@localhost \
--to=mjc@unre.st \
--cc=bcollins@debian.org \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linux1394-user@lists.sourceforge.net \
/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