netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: atl1-devel@lists.sourceforge.net, netdev@vger.kernel.org
Cc: jacliburn@bellsouth.net, greg@kroah.com
Subject: atl1 developers wanted
Date: Sun, 28 Oct 2007 02:33:28 -0400	[thread overview]
Message-ID: <47242D38.1050804@redhat.com> (raw)

Greetings, netdev!

	Since the Linux Driver Project apparently has a glut of talent, I figured I'd 
ask for a little help with an existing driver.  As some of you may know, Jay 
Cliburn and I have been working on atl1 since last summer, and we've gotten the 
driver merged and stable.  It does the basic things one expects a gigE driver to 
do, and it no longer does the things one expects a gigE driver to *not* do, but 
there are some hardware features that we don't support very well, or at all.

	If you have an atl1 board and want to get your hands dirty, we could use some 
help with the following:

Performance features:

TSO -- it works, but it's really slow, so we currently disable it by default
LRO -- would be nice to have
NAPI -- would be nice to have
configurable interrupt coalescing -- we're not currently taking advantage of this

feature testing:

jumbo frames -- last I checked, I could open connections with large MTU, but 
we've done very little validation, benchmarking, or optimization

IPv6 -- seems to work, but the hardware doesn't support offloading for IPv6 
traffic, so we need to know about the performance to prioritize work on the 
aforementioned performance features

other:

make WoLAN work reliably

	-- Chris

                 reply	other threads:[~2007-10-28  6:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47242D38.1050804@redhat.com \
    --to=csnook@redhat.com \
    --cc=atl1-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=jacliburn@bellsouth.net \
    --cc=netdev@vger.kernel.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).