netdev_rx_handler_register(9) [centos man page]

NETDEV_RX_HANDLER_RE(9) 				      Network device support					   NETDEV_RX_HANDLER_RE(9)

NAME

       netdev_rx_handler_register - register receive handler

SYNOPSIS

       int netdev_rx_handler_register(struct net_device * dev, rx_handler_func_t * rx_handler, void * rx_handler_data);

ARGUMENTS

       dev
	   device to register a handler for

       rx_handler
	   receive handler to register

       rx_handler_data
	   data pointer that is used by rx handler

DESCRIPTION

       Register a receive hander for a device. This handler will then be called from __netif_receive_skb. A negative errno code is returned on a
       failure.

       The caller must hold the rtnl_mutex.

       For a general description of rx_handler, see enum rx_handler_result.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   NETDEV_RX_HANDLER_RE(9)

REQUEST_THREADED_IRQ(9) 					Hardware Interfaces					   REQUEST_THREADED_IRQ(9)

NAME

       request_threaded_irq - allocate an interrupt line

SYNOPSIS

       int request_threaded_irq(unsigned int irq, irq_handler_t handler, irq_handler_t thread_fn, unsigned long irqflags, const char * devname,
				void * dev_id);

ARGUMENTS

       irq
	   Interrupt line to allocate

       handler
	   Function to be called when the IRQ occurs. Primary handler for threaded interrupts If NULL and thread_fn != NULL the default primary
	   handler is installed

       thread_fn
	   Function called from the irq handler thread If NULL, no irq thread is created

       irqflags
	   Interrupt type flags

       devname
	   An ascii name for the claiming device

       dev_id
	   A cookie passed back to the handler function

DESCRIPTION

       This call allocates interrupt resources and enables the interrupt line and IRQ handling. From the point this call is made your handler
       function may be invoked. Since your handler function must clear any interrupt the board raises, you must take care both to initialise your
       hardware and to set up the interrupt handler in the right order.

       If you want to set up a threaded irq handler for your device then you need to supply handler and thread_fn.  handler ist still called in
       hard interrupt context and has to check whether the interrupt originates from the device. If yes it needs to disable the interrupt on the
       device and return IRQ_WAKE_THREAD which will wake up the handler thread and run thread_fn. This split handler design is necessary to
       support shared interrupts.

       Dev_id must be globally unique. Normally the address of the device data structure is used as the cookie. Since the handler receives this
       value it makes sense to use it.

       If your interrupt is shared you must pass a non NULL dev_id as this is required when freeing the interrupt.

FLAGS

       IRQF_SHARED Interrupt is shared IRQF_DISABLED Disable local interrupts while processing IRQF_SAMPLE_RANDOM The interrupt can be used for
       entropy IRQF_TRIGGER_* Specify active edge(s) or level

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						   REQUEST_THREADED_IRQ(9)