From: Jeff Garzik <jeff@garzik.org>
To: Linsys Contractor Mithlesh Thukral <mithlesh@netxen.com>
Cc: netdev@vger.kernel.org, amitkale@netxen.com,
netxenproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 1/3] NetXen: Make driver use multiple PCI functions
Date: Tue, 06 Mar 2007 06:20:33 -0500 [thread overview]
Message-ID: <45ED4E81.6010408@garzik.org> (raw)
In-Reply-To: <200703051253.l25CrF7b004967@dut39.unminc.com>
Linsys Contractor Mithlesh Thukral wrote:
> NetXen: Make driver use multiple PCI functions.
> This patch will make NetXen driver work with multiple PCI functions. This will
> make the usage of memory resources as well as interrupts more independent
> among different functions which results in better throughput. This change has
> been done after the multiport capable firmware related changes are already
> there in the NetXen's driver in Linux.
>
> Signed-off by: Mithlesh Thukral <mithlesh@netxen.com>
>
> ---
>
> drivers/net/netxen/netxen_nic.h | 126 ++---
> drivers/net/netxen/netxen_nic_ethtool.c | 80 +--
> drivers/net/netxen/netxen_nic_hdr.h | 8
> drivers/net/netxen/netxen_nic_hw.c | 213 ++++++--
> drivers/net/netxen/netxen_nic_hw.h | 18
> drivers/net/netxen/netxen_nic_init.c | 115 +---
> drivers/net/netxen/netxen_nic_isr.c | 80 +--
> drivers/net/netxen/netxen_nic_main.c | 523 ++++++++++-----------
> drivers/net/netxen/netxen_nic_niu.c | 27 -
> drivers/net/netxen/netxen_nic_phan_reg.h | 125 -----
> 10 files changed, 631 insertions(+), 684 deletions(-)
applied 1-3 to #upstream (2.6.22)
next prev parent reply other threads:[~2007-03-06 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 12:53 [PATCH 1/3] NetXen: Make driver use multiple PCI functions Linsys Contractor Mithlesh Thukral
2007-03-06 11:20 ` Jeff Garzik [this message]
2007-03-08 12:47 ` Mithlesh Thukral
2007-03-08 13:12 ` Jeff Garzik
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=45ED4E81.6010408@garzik.org \
--to=jeff@garzik.org \
--cc=amitkale@netxen.com \
--cc=mithlesh@netxen.com \
--cc=netdev@vger.kernel.org \
--cc=netxenproj@linsyssoft.com \
--cc=rob@netxen.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).