From: Pete Popov <ppopov@embeddedalley.com>
To: Gilad Rom <gilad@romat.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Au1500 and 1Gbps
Date: Tue, 22 Mar 2005 10:47:02 -0800 [thread overview]
Message-ID: <42406826.2040302@embeddedalley.com> (raw)
In-Reply-To: <42406706.90409@romat.com>
Gilad Rom wrote:
> Hello,
>
> As a follow up to my last posting, I was wondering if anyone
> ever actually benchmarked the Au1500 in terms of networking
> throughput.
>
> We make a custom board, based on the Au1500. 100Mbps
> performance is 100% (100Mbps FTP transfers when using brctl to bridge
> both ethernet MAC's), but What we would like to do, ultimately,
> is build a board with two Gigabit MAC/PHY's and use our board
> to construct a much more powerful gateway.
>
> Any insight? can the Au1500 even try to handle 1000Mbps?
Should be easy to get up and running the benchmarked. The Intel 1G driver
(e100?) should run fine on mips with, hopefully, little or no modifications.
Pete
next prev parent reply other threads:[~2005-03-22 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 18:42 Au1500 and 1Gbps Gilad Rom
2005-03-22 18:47 ` Pete Popov [this message]
2005-03-22 18:51 ` Gilad Rom
2005-03-22 18:55 ` Pete Popov
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=42406826.2040302@embeddedalley.com \
--to=ppopov@embeddedalley.com \
--cc=gilad@romat.com \
--cc=linux-mips@linux-mips.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