netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: NAPI for eepro100

from [David S. Miller] [Permanent Link][Original]
To: jgarzik@xxxxxxxxxxxxxxxx
Subject: Re: NAPI for eepro100
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Wed, 12 Jun 2002 16:33:44 -0700 (PDT)
Cc: fxzhang@xxxxxxxxx, linux-mips@xxxxxxxxxxx, saw@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <3D07D6A6.7090308@xxxxxxxxxxxxxxxx>
References: <3D07D270.5060902@xxxxxxxxxxxxxxxx> <20020612.160532.134201977.davem@xxxxxxxxxx> <3D07D6A6.7090308@xxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx 
   From: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
   Date: Wed, 12 Jun 2002 19:17:58 -0400

   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 question is, do the descriptor bits have to live right before
the RX packet data buffer or can other schemes be used?
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: NAPI for eepro100, Jeff Garzik
Next by Date:  Re: [RFC] SNMP_ADD_STATS, Andi Kleen
Previous by Thread:  Re: NAPI for eepro100, Jeff Garzik
Next by Thread:  Re: NAPI for eepro100, Donald Becker
Indexes:  [Date] [Thread] [Top] [All Lists]