From: Donald Becker <becker@scyld.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>, <linux-mips@oss.sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<netdev@oss.sgi.com>
Subject: Re: NAPI for eepro100
Date: Wed, 12 Jun 2002 22:25:22 -0400 (EDT) [thread overview]
Message-ID: <ae9026$n00$2@main.gmane.org> (raw)
In-Reply-To: <20020612.163344.31410429.davem@redhat.com>
On Wed, 12 Jun 2002, David S. Miller wrote:
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> 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.
The eepro100 has a unique design in many different aspects.
> The question is, do the descriptor bits have to live right before
> the RX packet data buffer or can other schemes be used?
With the current driver structure, yes, the descriptor words must be
immediately before the packet data. You can use other Rx and Tx
structures/modes to avoid this, but they use less efficient memory access.
For instance, the current Tx structure allows transmitting a packet with
a single PCI burst, rather than multiple transfers.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993
next parent reply other threads:[~2002-06-13 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020612.163344.31410429.davem@redhat.com>
2002-06-13 2:25 ` Donald Becker [this message]
[not found] <3D0740ED.2060907@ict.ac.cn>
2002-06-12 23:00 ` NAPI for eepro100 Jeff Garzik
[not found] ` <3D07D270.5060902@mandrakesoft.com>
2002-06-12 23:05 ` David S. Miller
[not found] ` <20020612.160532.134201977.davem@redhat.com>
2002-06-12 23:17 ` Jeff Garzik
[not found] ` <3D07D6A6.7090308@mandrakesoft.com>
2002-06-12 23:33 ` David S. Miller
[not found] ` <20020613125753.A23693@castle.nmd.msu.ru>
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='ae9026$n00$2@main.gmane.org' \
--to=becker@scyld.com \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@oss.sgi.com \
--cc=netdev@oss.sgi.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).