From: Eugene Surovegin <ebs@ebshome.net>
To: ????????? <lonsn@163.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Re: Gigabit ethernet support of ppc440gx in 2.6 and 2.4
Date: Wed, 15 Feb 2006 20:49:48 -0800 [thread overview]
Message-ID: <20060216044948.GA23150@gate.ebshome.net> (raw)
In-Reply-To: <43F402AC.026BD0.10674>
On Thu, Feb 16, 2006 at 12:45:15PM +0800, ????????? wrote:
> Does the TCP/IP Acceleration Hardware of 440GX have been supported
> in official 2.6 kernel?
> How about the CPU utilization when you get 900+Mb/s? Since we want
> to do something such as simple datas codec at the same time.
My driver (both 2.4 and 2.6) supports TCP/UDP checksum offload. No TSO
yet.
I don't remember exact CPU load numbers, but it was less than 20% for
TX case (Ocotea was transmitting data).
--
Eugene
next parent reply other threads:[~2006-02-16 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43F402AC.026BD0.10674>
2006-02-16 4:49 ` Eugene Surovegin [this message]
2006-02-16 4:45 Re: Gigabit ethernet support of ppc440gx in 2.6 and 2.4 廖荣生
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=20060216044948.GA23150@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=lonsn@163.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).