From: Stephen Hemminger <shemminger@osdl.org>
To: "Linsys Contractor Amit S. Kale" <amitkale@netxen.com>
Cc: netdev@vger.kernel.org, brazilnut@us.ibm.com, jeff@garzik.org,
netxenproj@linsyssoft.com, rob@netxen.com, sanjeev@netxen.com,
wendyx@us.ibm.com
Subject: Re: [PATCH 3/3] NetXen: 64-bit memory fixes, driver cleanup
Date: Fri, 17 Nov 2006 08:40:49 -0800 [thread overview]
Message-ID: <20061117084049.555e14d0@localhost.localdomain> (raw)
In-Reply-To: <200611171536.kAHFa3os005563@dut39.unminc.com>
On Fri, 17 Nov 2006 07:36:03 -0800
"Linsys Contractor Amit S. Kale" <amitkale@netxen.com> wrote:
> NetXen: 1G/10G Ethernet Driver updates
> - These fixes take care of driver on machines with >4G memory
> - Driver cleanup
>
> Signed-off-by: Amit S. Kale <amitkale@netxen.com>
>
> netxen_nic.h | 41 ++++++----
> netxen_nic_ethtool.c | 19 ++--
> netxen_nic_hw.c | 10 +-
> netxen_nic_hw.h | 4
> netxen_nic_init.c | 51 +++++++++++-
> netxen_nic_isr.c | 3
> netxen_nic_main.c | 204 +++++++++++++++++++++++++++++++++++++++++++++++---
> netxen_nic_phan_reg.h | 10 +-
> 8 files changed, 293 insertions(+), 49 deletions(-)
>
If you can't DMA from high memory, then don't set NETIF_F_HIGHDMA, why do
you need explicit bounce buffers. If you can't DMA from unaligned address,
the write a small routine to copy the skb to a new one.
next prev parent reply other threads:[~2006-11-17 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 15:36 [PATCH 3/3] NetXen: 64-bit memory fixes, driver cleanup Linsys Contractor Amit S. Kale
2006-11-17 16:40 ` Stephen Hemminger [this message]
2006-11-18 10:28 ` Sanjeev Jorapur
2006-11-20 18:45 ` Stephen Hemminger
2006-11-23 16:32 ` Sanjeev Jorapur
2006-11-27 18:23 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2006-11-28 16:04 Amit S. Kale
2006-11-28 18:40 ` Stephen Hemminger
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=20061117084049.555e14d0@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=amitkale@netxen.com \
--cc=brazilnut@us.ibm.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=netxenproj@linsyssoft.com \
--cc=rob@netxen.com \
--cc=sanjeev@netxen.com \
--cc=wendyx@us.ibm.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).