From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: fxzhang@ict.ac.cn, linux-mips@oss.sgi.com, saw@saw.sw.com.sg,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: NAPI for eepro100
Date: Wed, 12 Jun 2002 19:17:58 -0400 [thread overview]
Message-ID: <ae8l62$6q3$2@main.gmane.org> (raw)
In-Reply-To: 20020612.160532.134201977.davem@redhat.com
David S. Miller wrote:
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> Date: Wed, 12 Jun 2002 19:00:00 -0400
>
> for the 'mips' patch, it looks
> like the arch maintainer(s) need to fix the PCI DMA support...
>
> No, it's worse than that.
>
> See how non-consistent memory is used by the eepro100 driver
> for descriptor bits? The skb->tail bits?
>
> That is very problematic.
Oh crap, you're right... eepro100 in general does funky stuff with the
way packets are handled, mainly due to the need to issue commands to the
NIC engine instead of the normal per-descriptor owner bit way of doing
things.
Well, I accept patches to that clean eepro100 up... I'm not terribly
motivated to clean it up myself, as we have e100 and an e100 maintainer
we can beat on if such uglies arise :)
Jeff
next prev parent reply other threads:[~2002-06-12 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 12:39 NAPI for eepro100 Zhang Fuxin
2002-06-12 23:00 ` Jeff Garzik
2002-06-12 23:00 ` Jeff Garzik
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:17 ` Jeff Garzik
2002-06-12 23:33 ` David S. Miller
2002-06-12 23:33 ` David S. Miller
2002-06-13 2:25 ` Donald Becker
2002-06-13 2:25 ` Donald Becker
2002-06-13 7:15 ` Samuel Maftoul
2002-06-19 11:46 ` Bill Davidsen
2002-06-13 2:25 ` Donald Becker
2002-06-12 23:33 ` David S. Miller
2002-06-12 23:17 ` Jeff Garzik [this message]
2002-06-13 8:57 ` Andrey Savochkin
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:57 ` Andrey Savochkin
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='ae8l62$6q3$2@main.gmane.org' \
--to=jgarzik@mandrakesoft.com \
--cc=davem@redhat.com \
--cc=fxzhang@ict.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@oss.sgi.com \
--cc=netdev@oss.sgi.com \
--cc=saw@saw.sw.com.sg \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.