linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: PPC440GX GigE support
Date: Mon, 19 Apr 2004 11:56:34 -0700	[thread overview]
Message-ID: <20040419115634.A19863@home.com> (raw)


I've pushed a bunch of code for this to the linux-2.5-ocp tree. It
overhauls the EMAC driver a bit and adds a number of fields to the
new OCP EMAC .additions field that are set per SoC or by the board
specific code.  There's support for GigE on EMAC2/3, the TAH,
zerocopy, and jumbo frames.

There's still work to be done on jumbo frames > 4062 MTU since
the RX side requires a copy. If we get some assumptions about
linear skbs in various protocol implementations removed, this can
be fixed. TSO support is the only major thing unimplemented.

Performance is right on par with an e1000 in the same platform,
showing anywhere from 700-850Mbps TX throughput depending on
MTU size and sendfile usage. RX range is slightly less.

Pull from bk://source.mvista.com/linux-2.5-ocp

Once the new OCP stuff goes into linux-2.5, I'll send some
version of this (plus previous EMAC driver work for 2.6) to
jgarzik.

-Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-04-19 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 18:56 Matt Porter [this message]
2004-04-26 11:28 ` PPC440GX GigE support Takeharu KATO
2004-05-03 18:36   ` Matt Porter
2004-06-14  2:58 ` LarrZheng
  -- strict thread matches above, loose matches on Subject: below --
2004-05-13 11:43 Phil Thompson

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=20040419115634.A19863@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.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).