Device Layer and Device Drivers COMS W6998 Spring 2010

advertisement
Device Layer and
Device Drivers
COMS W6998
Spring 2010
Erich Nahum
Device Layer vs. Device Driver

Linux tries to abstract away the device specifics
using the struct net_device

Provides a generic device layer in
linux/net/core/dev.c and
include/linux/netdevice.h

Device drivers are responsible for providing the
appropriate virtual functions



E.g., dev->netdev_ops->ndo_start_xmit
Device layer calls driver layer and vice-versa
Execution spans interrupts, syscalls, and softirqs
Device Interfaces
Higher Protocol Instances
dev.c
napi_schedule
dev_open
dev_queue_xmit
dev_close
Network devices
(adapter-independent)
Network devices
interface
net_device_ops
netdev_ops->ndo_open
netdev_ops->ndo_start_xmit
netdev_ops->ndo_stop
Abstraction from
Adapter specifics
pcnet32.c
pcnet32_interrupt
pcnet32_open
pcnet32_start_xmit
pcnet32_stop
Network driver
(adapter-specific)
Network Process Contexts

Hardware interrupt


Process context


Received packets (upcalls)
System calls (downcalls)
Softirq context


NET_RX_SOFTIRQ for received packets (upcalls)
NET_TX_SOFTIRQ for delayed sending packets
(downcalls)
Softnet



Introduced in kernel 2.4.x
Parallelize packet handling on SMP machines
Packet transmit/receive is handled via two softirqs:




NET_TX_SOFTIRQ feeds packets from network stack to
driver.
NET_RX_SOFTIRQ feeds packets from driver to network
stack.
The transmit/receive queues used to be stored in
per-cpu softnet_data.
Now stored in specific places:


Receive side: in device packet rx queues
Send side: in device qdiscs
Device Driver HW Interface

Driver
Memory
mapped
register
reads/
writes
Interrupts

Driver talks to the device:
 Writing commands to memory-mapped
control status registers
 Setting aside buffers for packet
transmission/reception
 Describing these buffers in descriptor
rings
Device talks to driver:
 Generating interrupts (both on send
and receive)
 Placing values in control status
registers
 DMA’ing packets to/from available
buffers
 Updating status in descriptor rings
Packet Descriptor Rings


Descriptors
contain
pointers,
status bits
Driver
allocates
packet
buffers
TX
Descriptor
Ring
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
SendErr
RX
Descriptor
Ring
TXQ
Tail
Sent
Send
Free
RXQ
Head
Packet
Buffer
RecvOK
Send
RecvOK
Send
RcvErr
Free
TXQ
Head
Free
Packet
Buffer
Free
Free
RecvCRC
RecvOK
RXQ
Tail
Free
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
Packet
Buffer
NIC IRQ

The NIC registers an interrupt handler with the IRQ
with which the device works by calling
request_irq().




This interrupt handler is the one that will be called when a
frame is received
The same interrupt handler may be called for other
reasons (depends, NIC-dependent)
 Transmission complete, transmission error
Newer drivers (e.g., e1000e) seem to use Message
Sequenced Interrupts (MSI), which use different interrupt
numbers
Device drivers can release an IRQ using free_irq
.
Packet Reception with NAPI

Originally, Linux took one interrupt per received
packet




NAPI: “New API”
With NAPI, interrupt notifies softnet layer
(NET_RX_SOFTIRQ) that packets are available
Driver requirements:




This could cause excessive overhead under heavy loads
Ability to turn receive interrupts off and back on again
A ring buffer
A poll function to pull packets out
Most drivers support this now.
Reception: NAPI mode (1)



NAPI allows dynamic switching:
 To polled mode when the interrupt rate is too high
 To interrupt-driven when load is low
In the network interface private structure, add a struct
napi_struct
At driver initialization, register the NAPI poll operation:
netif_napi_add(dev, &bp->napi, my_poll, 64);
 dev is the network interface
 &bp->napi is the struct napi_struct
 my_poll is the NAPI poll operation
 64 is the weight that represents the importance of the
network interface. It is related to the threshold below which
the driver will return back to interrupt mode.
Reception: NAPI mode (2)

In the interrupt handler, when a packet has been received:
if (napi_schedule_prep(&bp->napi)) {
/* Disable reception interrupts */
__napi_schedule(& bp->napi);
}
The kernel will call our poll() operation regularly
The poll() operation has the following prototype:
 static int my_poll(struct napi_struct *napi, int
budget)
It must receive at most budget packets and push them to the
network stack using netif_receive_skb().
If fewer than budget packets have been received, switch back to
interrupt mode using napi_complete(& bp->napi) and
reenable interrupts
Poll function must return the number of packets received





Receiving Data Packets (1)

dev.c
napi_schedule

‘‘hard“
IRQ
pcnet32.c
pcnet32_interrupt
HW interrupt invokes
__do_IRQ
__do_IRQ invokes each
handler for that IRQ:

irq/handle.c
__do_IRQ
interrupt

action->handler(irq,
action->dev_id);
pcnet_32_interrupt



Acknowledge intr ASAP
Checks various registers
Calls napi_schedule to
wake up
NET_RX_SOFTIRQ
Receiving Data Packets (2)

arp_rcv
ip_rcv
..
ipx_rcv

dev.c
ptype_base[ntohs(type)]
soft
IRQ
Immediately after the interrupt,
do_softirq is run
netif_receive_skb

For each napi struct in the list
(one per dev)


pcnet32.c
pcnet32_poll

dev.c
softirq.c
net_rx_action
do_softirq
Scheduler
Recall softirqs are per-cpu
Invoke poll function
Track amount of work done
(packets)
If work threshold exceeded, wake
up softirqd and break out of loop
Receiving Data Packets (3)

arp_rcv
ip_rcv
..
Driver poll function:

ipx_rcv
dev.c

ptype_base[ntohs(type)]
soft
IRQ
netif_receive_skb


netif_receive_skb:

pcnet32.c
pcnet32_poll
dev.c
softirq.c
net_rx_action
do_softirq
Scheduler
may call dev_alloc_skb and
copy
 pcnet32 does, e1000 doesn’t.
Does call netif_receive_skb
Clears tx ring and frees sent skbs

Calls eth_type_trans to get
packet type
 skb_pull the ethernet
header (14 bytes)
 Data now points to payload
data (e.g., IP header)
Demultiplexes to appropriate
receive function based on header
type
Packet Types Hash Table
ptype_base[16]
A protocol that
receives only packets
with the correct packet
identifier
0
1
16
ptype_all
packet_type
type: ETH_P_ARP
dev: NULL
func
...
list
packet_type
type: ETH_P_IP
dev: NULL
func
...
list
...
packet_type
packet_type
type: ETH_P_ALL
dev
func
...
list
arp_rcv()
packet_type
ip_rcv()
A protocol that
receives all packets
arriving at the
interface
packet_type
type: ETH_P_ALL
dev
func
...
list
Transmission Overview



Transmission is surprisingly complex
Each net_device has 1 or more tx queues
Each queue has a policy associated with it


struct Qdisc
Polices can be simple


Policies can be very complex


e.g., default pfifo, stochastic fairness queuing
e.g., RED, Hierarchical Token Bucket
In this section, we assume PFIFO.
Queuing Ops

enqueue()



Enqueues a packet
dequeue()
 Returns a pointer to a packet (skb) eligible for
sending; NULL means nothing is ready
pfifo – 3 band priority fifo


Enqueue function is pfifo_fast_enqueue
Dequeue function is pfifo_fast_dequeue
Sending a Packet Direct (1)
dev.c
dev_queue_xmit

sched_generic.c
dev_queue_xmit


dev->qdisc->pfifo_fast_enqueue

__qdisc_run
Syscall
or
soft
IRQ
qdisc_restart
dev->qdisc->pfifo_fast_dequeue


dev_hard_start_xmit
pcnet32.c
pcnet32_start_xmit
If not, calls
dev_hard_start_xmit
dev->q->enqueue(pfifo)


dev.c
Linearizes skb if nec
Checksums if nec
Calls q->enqueue if avail

Checks queue length
Drops if necessary
Adds to tail otherwise
Sending a Packet Direct (2)
dev.c
dev_queue_xmit


sched_generic.c
dev->qdisc->pfifo_fast_enqueue


__qdisc_run
Syscall
or
soft
IRQ
__qdisc_run
Qdisc_restart


qdisc_restart
dev->qdisc->pfifo_fast_dequeue



dev_hard_start_xmit

pcnet32.c
pcnet32_start_xmit
Dequeues a packet
Finds tx queue
Calls
dev_hard_start_xmit
dev_hard_start_xmit

dev.c
Calls qdisc_restart until
error
Enables tx softirq if nec
Invokes dev->xmit
Frees the skb
pcnet32_start_xmit

Puts skb in tx descriptor ring
Sending a Packet via SoftIRQ
softirq.c
dev.c
do_softirq

do_softirq invoked

net_tx_action is the
action for
NET_TX_SOFTIRQ
net_tx_action

net_tx_action
sched_generic.c
__qdisc_run

soft
IRQ
qdisc_restart

dev->qdisc->pfifo_fast_dequeue

dev.c
dev_hard_start_xmit
pcnet32.c
pcnet32_start_xmit
Frees packets posted to
completion queue
Invokes __qdisc_run on
all output qdiscs if possible
Sets bit in qdisc to run
again if necessary
Download