Re-entrant code in network drivers (cross-post)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I am trying to understand the issues in writing a driver that is 
re-entrant. What are the locking issues involved (if any)?

For example, if there are say 4 3com network cards in a box, I would 
assume that the same piece of 3com driver code is being used by all 4 of 
them. They would be sharing (all?) the code. Now if packets arrive to each 
of the cards, how does the kernel handle processing these packets thru the 
same code to avoid messing up the device queues?

Any code examples, pointers, tutorials are most welcome.

Regards,
Amit
-- 
The statement below is true.
The statement above is false.
^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
                  Amit Kucheria
          EECS Grad. Research Assistant
         University of Kansas @ Lawrence
   (R)+1-(785)-830 8521 ||| (O)+1-(785)-864 7774
____________________________________________________


-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux