linux device drivers 2nd edition phần 9 ppt

err or, memory corruption is so harmful to the system that the developers decided to take definitive action. In practice, you shouldn’t need to check the available space if the buffer has been correctly allocated. Since drivers usually get the packet size before allocating a buffer, only a severely broken driver will put too much data in the buffer, and a panic might be seen as due pun- ishment. int skb_headroom(struct sk_buff *skb); Retur ns the amount of space available in front of data, that is, how many octets one can “push” to the buffer. void skb_reserve(struct sk_buff *skb, int len); This function increments both data and tail. The function can be used to reserve headroom before filling the buffer. Most Ethernet interfaces reserve 2 bytes in front of the packet; thus, the IP header is aligned on a 16-byte bound- ary, after a 14-byte Ethernet header. snull does this as well, although the instruction was not shown in “Packet Reception” to avoid introducing extra concepts at that point. unsigned char *skb_pull(struct sk_buff *skb, int len); Removes data from the head of the packet. The driver won’t need to use this function, but it is included here for completeness. It decrements skb->len and increments skb->data; this is how the hardware header (Ethernet or equivalent) is stripped from the beginning of incoming packets. The kernel defines several other functions that act on socket buffers, but they are meant to be used in higher layers of networking code, and the driver won’t need them. MAC Address Resolution An interesting issue with Ethernet communication is how to associate the MAC addr esses (the interface’s unique hardware ID) with the IP number. Most protocols have a similar problem, but we concentrate on the Ethernet-like case here. We’ll try to offer a complete description of the issue, so we will show three situations: ARP, Ether net headers without ARP (like plip), and non-Ethernet headers. Using ARP with Ethernet The usual way to deal with address resolution is by using ARP, the Address Reso- lution Protocol. Fortunately, ARP is managed by the kernel, and an Ethernet inter- face doesn’t need to do anything special to support ARP. As long as dev->addr and dev->addr_len ar e corr ectly assigned at open time, the driver doesn’t need to worry about resolving IP numbers to physical addresses; ether_setup assigns the corr ect device methods to dev->hard_header and dev->rebuild_header. MAC Address Resolution 455 22 June 2001 16:43 Chapter 14: Network Drivers Although the kernel normally handles the details of address resolution (and caching of the results), it calls upon the interface driver to help in the building of the packet. After all, the driver knows about the details of the physical layer header, while the authors of the networking code have tried to insulate the rest of the kernel from that knowledge. To this end, the kernel calls the driver’s har d_header method to lay out the packet with the results of the ARP query. Nor- mally, Ethernet driver writers need not know about this process — the common Ether net code takes care of everything. Over r iding ARP Simple point-to-point network interfaces such as plip might benefit from using Eth- er net headers, while avoiding the overhead of sending ARP packets back and forth. The sample code in snull also falls into this class of network devices. snull cannot use ARP because the driver changes IP addresses in packets being transmit- ted, and ARP packets exchange IP addresses as well. Although we could have implemented a simple ARP reply generator with little trouble, it is more illustrative to show how to handle physical-layer headers directly. If your device wants to use the usual hardware header without running ARP, you need to override the default dev->hard_header method. This is how snull implements it, as a very short function. int snull_header(struct sk_buff *skb, struct net_device *dev, unsigned short type, void *daddr, void *saddr, unsigned int len) { struct ethhdr *eth = (struct ethhdr *)skb_push(skb,ETH_HLEN); eth->h_proto = htons(type); memcpy(eth->h_source, saddr ? saddr : dev->dev_addr, dev->addr_len); memcpy(eth->h_dest, daddr ? daddr : dev->dev_addr, dev->addr_len); eth->h_dest[ETH_ALEN-1] ˆ= 0x01; /* dest is us xor 1 */ return (dev->hard_header_len); } The function simply takes the information provided by the kernel and formats it into a standard Ethernet header. It also toggles a bit in the destination Ethernet addr ess, for reasons described later. When a packet is received by the interface, the hardware header is used in a cou- ple of ways by eth_type_trans. We have already seen this call in snull_rx: skb->protocol = eth_type_trans(skb, dev); The function extracts the protocol identifier (ETH_P_IP in this case) from the Eth- er net header; it also assigns skb->mac.raw, removes the hardware header from 456 22 June 2001 16:43 packet data (with skb_ pull), and sets skb->pkt_type. This last item defaults to PACKET_HOST at skb allocation (which indicates that the packet is directed to this host), and eth_type_trans changes it according to the Ethernet destination addr ess. If that address does not match the address of the interface that received it, the pkt_type field will be set to PACKET_OTHERHOST. Subsequently, unless the inter face is in promiscuous mode, netif_rx will drop any packet of type PACKET_OTHERHOST. For this reason, snull_header is careful to make the desti- nation hardware addr ess match that of the “receiving” interface. If your interface is a point-to-point link, you won’t want to receive unexpected multicast packets. To avoid this problem, remember that a destination address whose first octet has 0 as the least significant bit (LSB) is directed to a single host (i.e., it is either PACKET_HOST or PACKET_OTHERHOST). The plip driver uses 0xfc as the first octet of its hardware addr ess, while snull uses 0x00. Both addr esses result in a working Ethernet-like point-to-point link. Non-Ether net Header s We have just seen that the hardware header contains some information in addition to the destination address, the most important being the communication protocol. We now describe how hardware headers can be used to encapsulate relevant infor mation. If you need to know the details, you can extract them from the kernel sources or the technical documentation for the particular transmission medium. Most driver writers will be able to ignore this discussion and just use the Ethernet implementation. It’s worth noting that not all information has to be provided by every protocol. A point-to-point link such as plip or snull could avoid transferring the whole Ether- net header without losing generality. The har d_header device method, shown ear- lier as implemented by snull_header, receives the delivery information — both pr otocol-level and hardware addr esses—from the kernel. It also receives the 16-bit pr otocol number in the type argument; IP, for example, is identified by ETH_P_IP. The driver is expected to correctly deliver both the packet data and the protocol number to the receiving host. A point-to-point link could omit addr esses fr om its hardware header, transferring only the protocol number, because delivery is guaranteed independent of the source and destination addr esses. An IP-only link could even avoid transmitting any hardware header whatsoever. When the packet is picked up at the other end of the link, the receiving function in the driver should correctly set the fields skb->protocol, skb->pkt_type, and skb->mac.raw. skb->mac.raw is a char pointer used by the address-r esolution mechanism implemented in higher layers of the networking code (for instance, net/ipv4/arp.c). MAC Address Resolution 457 22 June 2001 16:43 Chapter 14: Network Drivers It must point to a machine address that matches dev->type. The possible values for the device type are defined in <linux/if_arp.h>; Ether net inter faces use ARPHRD_ETHER. For example, here is how eth_type_trans deals with the Ethernet header for received packets: skb->mac.raw = skb->data; skb_pull(skb, dev->hard_header_len); In the simplest case (a point-to-point link with no headers), skb->mac.raw can point to a static buffer containing the hardware addr ess of this interface, proto- col can be set to ETH_P_IP, and packet_type can be left with its default value of PACKET_HOST. Because every hardware type is unique, it is hard to give more specific advice than already discussed. The kernel is full of examples, however. See, for example, the AppleTalk driver (drivers/net/appletalk/cops.c), the infrared drivers (such as drivers/net/ir da/smc_ircc.c), or the PPP driver (drivers/net/ppp_generic.c). Custom ioctl Commands We have seen that the ioctl system call is implemented for sockets; SIOCSIFADDR and SIOCSIFMAP ar e examples of “socket ioctls.” Now let’s see how the third argument of the system call is used by networking code. When the ioctl system call is invoked on a socket, the command number is one of the symbols defined in <linux/sockios.h>, and the function sock_ioctl dir ectly invokes a protocol-specific function (where “pr otocol” refers to the main network protocol being used, for example, IP or AppleTalk). Any ioctl command that is not recognized by the protocol layer is passed to the device layer. These device-related ioctl commands accept a third argument from user space, a struct ifreq *. This structure is defined in <linux/if.h>. The SIOCSIFADDR and SIOCSIFMAP commands actually work on the ifreq structur e. The extra argument to SIOCSIFMAP, although defined as ifmap, is just a field of ifreq. In addition to using the standardized calls, each interface can define its own ioctl commands. The plip inter face, for example, allows the interface to modify its inter- nal timeout values via ioctl. The ioctl implementation for sockets recognizes 16 commands as private to the interface: SIOCDEVPRIVATE thr ough SIOCDEVPRI- VATE+15. When one of these commands is recognized, dev->do_ioctl is called in the rel- evant interface driver. The function receives the same struct ifreq * pointer that the general-purpose ioctl function uses: int (*do_ioctl)(struct net_device *dev, struct ifreq *ifr, int cmd); 458 22 June 2001 16:43 The ifr pointer points to a kernel-space address that holds a copy of the struc- tur e passed by the user. After do_ioctl retur ns, the structure is copied back to user space; the driver can thus use the private commands to both receive and retur n data. The device-specific commands can choose to use the fields in struct ifreq, but they already convey a standardized meaning, and it’s unlikely that the driver can adapt the structure to its needs. The field ifr_data is a caddr_t item (a pointer) that is meant to be used for device-specific needs. The driver and the pro- gram used to invoke its ioctl commands should agree about the use of ifr_data. For example, pppstats uses device-specific commands to retrieve information from the ppp inter face driver. It’s not worth showing an implementation of do_ioctl her e, but with the informa- tion in this chapter and the kernel examples, you should be able to write one when you need it. Note, however, that the plip implementation uses ifr_data incorr ectly and should not be used as an example for an ioctl implementation. Statistical Infor mation The last method a driver needs is get_stats. This method retur ns a pointer to the statistics for the device. Its implementation is pretty easy; the one shown works even when several interfaces are managed by the same driver, because the statis- tics are hosted within the device data structure. struct net_device_stats *snull_stats(struct net_device *dev) { struct snull_priv *priv = (struct snull_priv *) dev->priv; return &priv->stats; } The real work needed to retur n meaningful statistics is distributed throughout the driver, wher e the various fields are updated. The following list shows the most inter esting fields in struct net_device_stats. unsigned long rx_packets; unsigned long tx_packets; These fields hold the total number of incoming and outgoing packets success- fully transferred by the interface. unsigned long rx_bytes; unsigned long tx_bytes; The number of bytes received and transmitted by the interface. These fields wer e added in the 2.2 kernel. Statistical Infor mation 459 22 June 2001 16:43 Chapter 14: Network Drivers unsigned long rx_errors; unsigned long tx_errors; The number of erroneous receptions and transmissions. There’s no end of things that can go wrong with packet transmission, and the net_device_stats structur e includes six counters for specific receive err ors and five for transmit errors. See <linux/netdevice.h> for the full list. If possible, your driver should maintain detailed error statistics, because they can be most helpful to system administrators trying to track down a prob- lem. unsigned long rx_dropped; unsigned long tx_dropped; The number of packets dropped during reception and transmission. Packets ar e dr opped when there’s no memory available for packet data. tx_dropped is rarely used. unsigned long collisions; The number of collisions due to congestion on the medium. unsigned long multicast; The number of multicast packets received. It is worth repeating that the get_stats method can be called at any time—even when the interface is down—so the driver should not release statistic information when running the stop method. Multicasting A multicast packet is a network packet meant to be received by more than one host, but not by all hosts. This functionality is obtained by assigning special hard- war e addr esses to groups of hosts. Packets directed to one of the special addresses should be received by all the hosts in that group. In the case of Ethernet, a multi- cast address has the least significant bit of the first address octet set in the destina- tion address, while every device board has that bit clear in its own hardware addr ess. The tricky part of dealing with host groups and hardware addr esses is perfor med by applications and the kernel, and the interface driver doesn’t need to deal with these problems. Transmission of multicast packets is a simple problem because they look exactly like any other packets. The interface transmits them over the communication medium without looking at the destination address. It’s the kernel that has to assign a correct hardware destination address; the har d_header device method, if defined, doesn’t need to look in the data it arranges. 460 22 June 2001 16:43 The kernel handles the job of tracking which multicast addresses are of inter est at any given time. The list can change frequently, since it is a function of the applica- tions that are running at any given time and the user’s interest. It is the driver’s job to accept the list of interesting multicast addresses and deliver to the kernel any packets sent to those addresses. How the driver implements the multicast list is somewhat dependent on how the underlying hardware works. Typically, hardware belongs to one of three classes, as far as multicast is concerned: • Inter faces that cannot deal with multicast. These interfaces either receive pack- ets directed specifically to their hardware addr ess (plus broadcast packets), or they receive every packet. They can receive multicast packets only by receiv- ing every packet, thus potentially overwhelming the operating system with a huge number of “uninteresting” packets. You don’t usually count these inter- faces as multicast capable, and the driver won’t set IFF_MULTICAST in dev->flags. Point-to-point interfaces are a special case, because they always receive every packet without perfor ming any hardware filtering. • Inter faces that can tell multicast packets from other packets (host-to-host or br oadcast). These interfaces can be instructed to receive every multicast packet and let the software deter mine if this host is a valid recipient. The over- head introduced in this case is acceptable, because the number of multicast packets on a typical network is low. • Inter faces that can perfor m hardwar e detection of multicast addresses. These inter faces can be passed a list of multicast addresses for which packets are to be received, and they will ignore other multicast packets. This is the optimum case for the kernel, because it doesn’t waste processor time dropping “uninter- esting” packets received by the interface. The kernel tries to exploit the capabilities of high-level interfaces by supporting at its best the third device class, which is the most versatile. Therefor e, the kernel notifies the driver whenever the list of valid multicast addresses is changed, and it passes the new list to the driver so it can update the hardware filter according to the new information. Kernel Support for Multicasting Support for multicast packets is made up of several items: a device method, a data structur e and device flags. void (*dev->set_multicast_list)(struct net_device *dev); This device method is called whenever the list of machine addresses associ- ated with the device changes. It is also called when dev->flags is modified, because some flags (e.g., IFF_PROMISC) may also requir e you to repr ogram the hardware filter. The method receives a pointer to struct net_device as an argument and retur ns void. A driver not interested in implementing this Multicasting 461 22 June 2001 16:43 Chapter 14: Network Drivers method can leave the field set to NULL. struct dev_mc_list *dev->mc_list; This is a linked list of all the multicast addresses associated with the device. The actual definition of the structure is intr oduced at the end of this section. int dev->mc_count; The number of items in the linked list. This information is somewhat redun- dant, but checking mc_count against 0 is a useful shortcut for checking the list. IFF_MULTICAST Unless the driver sets this flag in dev->flags, the interface won’t be asked to handle multicast packets. The set_multicast_list method will nonetheless be called when dev->flags changes, because the multicast list may have changed while the interface was not active. IFF_ALLMULTI This flag is set in dev->flags by the networking software to tell the driver to retrieve all multicast packets from the network. This happens when multi- cast routing is enabled. If the flag is set, dev->mc_list shouldn’t be used to filter multicast packets. IFF_PROMISC This flag is set in dev->flags when the interface is put into promiscuous mode. Every packet should be received by the interface, independent of dev->mc_list. The last bit of information needed by the driver developer is the definition of struct dev_mc_list, which lives in <linux/netdevice.h>. struct dev_mc_list { struct dev_mc_list *next; /* Next address in list */ _ _u8 dmi_addr[MAX_ADDR_LEN]; /* Hardware address */ unsigned char dmi_addrlen; /* Address length */ int dmi_users; /* Number of users */ int dmi_gusers; /* Number of groups */ }; Because multicasting and hardware addr esses ar e independent of the actual trans- mission of packets, this structure is portable across network implementations, and each address is identified by a string of octets and a length, just like dev->dev_addr. A Typical Implementation The best way to describe the design of set_multicast_list is to show you some pseudocode. 462 22 June 2001 16:43 The following function is a typical implementation of the function in a full-fea- tur ed (ff) driver. The driver is full featured in that the interface it controls has a complex hardware packet filter, which can hold a table of multicast addresses to be received by this host. The maximum size of the table is FF_TABLE_SIZE. All the functions prefixed with ff_ ar e placeholders for hardware-specific opera- tions. void ff_set_multicast_list(struct net_device *dev) { struct dev_mc_list *mcptr; if (dev->flags & IFF_PROMISC) { ff_get_all_packets(); return; } /* If there’s more addresses than we handle, get all multicast packets and sort them out in software. */ if (dev->flags & IFF_ALLMULTI || dev->mc_count > FF_TABLE_SIZE) { ff_get_all_multicast_packets(); return; } /* No multicast? Just get our own stuff */ if (dev->mc_count == 0) { ff_get_only_own_packets(); return; } /* Store all of the multicast addresses in the hardware filter */ ff_clear_mc_list(); for (mc_ptr = dev->mc_list; mc_ptr; mc_ptr = mc_ptr->next) ff_store_mc_address(mc_ptr->dmi_addr); ff_get_packets_in_multicast_list(); } This implementation can be simplified if the interface cannot store a multicast table in the hardware filter for incoming packets. In that case, FF_TABLE_SIZE reduces to 0 and the last four lines of code are not needed. As was mentioned earlier, even interfaces that can’t deal with multicast packets need to implement the set_multicast_list method to be notified about changes in dev->flags. This approach could be called a “nonfeatured” (nf) implementa- tion. The implementation is very simple, as shown by the following code: void nf_set_multicast_list(struct net_device *dev) { if (dev->flags & IFF_PROMISC) nf_get_all_packets(); else nf_get_only_own_packets(); } Multicasting 463 22 June 2001 16:43 Chapter 14: Network Drivers Implementing IFF_PROMISC is important, because otherwise the user won’t be able to run tcpdump or any other network analyzers. If the interface runs a point- to-point link, on the other hand, there’s no need to implement set_multicast_list at all, because users receive every packet anyway. Backward Compatibility Version 2.3.43 of the kernel saw a major rework of the networking subsystem. The new “softnet” implementation was a great improvement in terms of perfor mance and clean design. It also, of course, brought changes to the network driver inter- face — though fewer than one might have expected. Differences in Linux 2.2 First of all, Linux 2.3.14 renamed the network device structure, which had always been struct device,tostruct net_device. The new name is certainly mor e appr opriate, since the structure was never meant to describe devices in gen- eral. Prior to version 2.3.43, the functions netif_start_queue, netif_stop_queue, and netif_wake_queue did not exist. Packet transmission was, instead, controlled by thr ee fields in the device structur e, and sysdep.h implements the three functions using the three fields when compiling for 2.2 or 2.0. unsigned char start; This variable indicated that the interface was ready for operations; it was nor- mally set to 1 in the driver’s open method. The current implementation is to call netif_start_queue instead. unsigned long interrupt; interrupt was used to indicate that the device was servicing an interrupt— accordingly, it was set to 1 at the beginning of the interrupt handler and to 0 befor e retur ning. It was never a substitute for proper locking, and its use has been replaced with internal spinlocks. unsigned long tbusy; When nonzero, this variable indicated that the device could handle no more outgoing packets. Where a 2.4 driver will call netif_stop_queue, older drivers would set tbusy to 1. Restarting the queue requir ed setting tbusy back to 0 and calling mark_bh(NET_BH). Nor mally, setting tbusy was sufficient to ensure that the driver’s har d_start_xmit method would not be called. However, if the networking system decided that a transmitter lockup must have occurred, it would call that method anyway. There was no tx_timeout method before softnet was integrated. Thus, pre-softnet drivers had to explicitly check for a call to har d_start_xmit when tbusy was set and react accordingly. 464 22 June 2001 16:43 [...]... fields in the net _device and sk_buff structures, however, are not repeated here #include This header hosts the definitions of struct net _device and struct net _device_ stats, and includes a few other headers that are needed by network drivers int register_netdev(struct net _device *dev); void unregister_netdev(struct net _device *dev); Register and unregister a network device SET_MODULE_OWNER(struct... up to 32 devices, and each device can be a multifunction board (such as an audio device with an accompanying CD-ROM drive) with a maximum of eight functions Each function can thus be identified at hardware level by a 16-bit address, or key Device drivers written for Linux, though, don’t need to deal with those binary addresses as they use a specific data structure, called pci_dev, to act on the devices... As suggested, the user can look at the PCI device list and the devices’ configuration registers by reading /pr oc/bus/pci/devices and /pr oc/bus/pci/*/* The former is a text file with (hexadecimal) device information, and the latter are binary files that report a snapshot of the configuration registers of each device, one file per device * You’ll find the ID of any device in its own hardware manual A list... on a bus /device pair The devfn argument represents both the device and function items Its use is extremely rare (drivers should not care about which slot their device is plugged into); it is listed here just for completeness Based on this information, initialization for a typical device driver that handles a single device type will look like the following code The code is for a hypothetical device jail... pci_find_class requires that jail_find_all_devices perform a little more work than in the example The function should check the newly found device against a list of vendor /device pairs, possibly using dev->vendor and dev- >device Its core should look like this: struct devid {unsigned short vendor, device} devlist[] = { {JAIL_VENDOR1, JAIL _DEVICE1 }, {JAIL_VENDOR2, JAIL _DEVICE2 }, /* */ { 0, 0 } }; /* */ for... that each device board can host up to eight devices; each device uses a single interrupt pin and reports it in its own configuration register Different devices on the same device board can use different interrupt pins or share the same one The PCI_INTERRUPT_LINE register, on the other hand, is read/write When the computer is booted, the firmware scans its PCI devices and sets the register for each device. .. those devices that can be added to or removed from the system while the system runs (such as CardBus devices) The material introduced in this section is not available in 2.2 and earlier kernels, but is the preferred way to go for newer drivers The basic idea being exploited is that whenever a new device appears during the system’s lifetime, all available device drivers must check whether the new device. .. hot-plug-aware device driver must register an object with the kernel, and the pr obe function for the object will be asked to check any device in the system to take hold of it or leave it alone This approach has no downside: the usual case of a static device list is handled by scanning the device list once for each device at system boot; modularized drivers will just unload as usual if no device is there,... and encapsulated into a socket buffer #include Included by netdevice.h, this file declares the interface flags (IFF_ macros) and struct ifmap, which has a major role in the ioctl implementation for network drivers void netif_carrier_off(struct net _device *dev); void netif_carrier_on(struct net _device *dev); int netif_carrier_ok(struct net _device *dev); The first two functions may be used... specific device registers (in the device I/O regions, introduced later) • Before accessing any device resource (I/O region or interrupt), the driver must call pci_enable _device If the additional probing just discussed requires accessing device I/O or memory space, the function must be called before such probing takes place • A network interface driver should make dev->driver_data point to the struct net_device . might have expected. Differences in Linux 2.2 First of all, Linux 2.3.14 renamed the network device structure, which had always been struct device, tostruct net _device. The new name is certainly mor. in the net _device and sk_buff structur es, however, are not repeated her e. #include < ;linux/ netdevice.h> This header hosts the definitions of struct net _device and struct net _device_ stats,. by network drivers. int register_netdev(struct net _device *dev); void unregister_netdev(struct net _device *dev); Register and unregister a network device. SET_MODULE_OWNER(struct net _device *dev); This