From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Eliezer Tamir" <eliezert@broadcom.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"jeff@garzik.org" <jeff@garzik.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Michael Chan" <mchan@broadcom.com>,
eilong@broadcom.com, vladz@broadcom.com, gertner@broadcom.com
Subject: Re: [BNX2X RESUBMIT][PATCH 0/8] New driver for Broadcom 10Gb Ethernet, take two.
Date: Mon, 8 Oct 2007 10:29:19 -0700 [thread overview]
Message-ID: <20071008102919.1cbc7983@freepuppy.rosehill> (raw)
In-Reply-To: <470A23E5.6030102@broadcom.com>
On Mon, 08 Oct 2007 14:34:45 +0200
"Eliezer Tamir" <eliezert@broadcom.com> wrote:
> [resubmitting, this time without line breaks, sorry]
>
> This is an initial version of the BNX2X, the Linux driver for the
> BCM5771X 10Gb Ethernet controller family.
>
> Although the chip is very different from the 5706-8 family we based the
> driver code on the BNX2 driver.
>
> Since the hardware is supposed to be generally available soon I have
> posted an initial version and after hearing all the comments I am
> reposting with changes to address them.
>
> Some planned feature are still under development, but we want to get
> whatever we have out now so people can start using the HW.
>
> Main changes from first version.
>
> * Fixed most issues raised by Michael Buesch. (Thanks Michael!)
> * Some slow path bug fixes.
> * Yitchak Gertner re-grouped the code in a more logical manner.
> * A lot of work was done to get the generated code to comply with coding
> style requirements.
>
> Known issues/TODO.
> * Move slowpath event handling from tasklet to workqueue context. This
> will allow replacing the busy waits in the link management code with sleeps.
>
> Please consider applying to 2.6.24
>
> Thanks
> Eliezer
Looks good. Some minor stuff:
* You can use network device stats in network device structure and
no longer need the copy in bp
* The MACRO's for 64 bit stats look like they could be done with
u64 and/or turned into inline's.
* RCS/CVS tags for date and version # are kind of ugly. They git system
doesn't use them, perhaps you just want to track your internal version
control information, but what happens when changes come from outside?
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-08 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 12:34 [BNX2X RESUBMIT][PATCH 0/8] New driver for Broadcom 10Gb Ethernet, take two Eliezer Tamir
2007-10-08 13:02 ` Matti Aarnio
2007-10-08 16:17 ` Randy Dunlap
2007-10-08 17:29 ` Stephen Hemminger [this message]
2007-10-08 18:34 ` Eliezer
2007-10-08 19:08 ` Stephen Hemminger
2007-10-08 19:18 ` Eliezer Tamir
2007-10-08 21:40 ` Michael Chan
2007-10-08 21:03 ` Stephen Hemminger
2007-10-08 21:28 ` David Miller
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=20071008102919.1cbc7983@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=eliezert@broadcom.com \
--cc=gertner@broadcom.com \
--cc=jeff@garzik.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.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