lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130115005247.GB18654@debian.localdomain>
Date:	Tue, 15 Jan 2013 08:52:47 +0800
From:	horseriver <horserivers@...il.com>
To:	Rami Rosen <roszenrami@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: what is the use of poll function int a net_device struct

On Tue, Jan 15, 2013 at 03:20:39PM +0200, Rami Rosen wrote:
> Hi,
> 
> On Mon, Jan 14, 2013 at 4:21 PM, horseriver <horserivers@...il.com> wrote:
> > Where is the handler function defined  for an netcard's  IRQ
> 
> look for the request_irq() method; you register the handler with this method.
> 
> for example,
> in e1000e:
> 
> http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/e1000e/netdev.c
> 
> err = request_irq(adapter->msix_entries[vector].vector,
>                            e1000_intr_msix_rx, 0,
>                           adapter->rx_ring->name,
>                              netdev);
> 
> so the handler is   e1000_intr_msix_rx().
> 
> When an IRQ has reached,  how to wake_up the wait_queue of the socket?
> TCP/UDP packet goes up from the driver to L3 and then to L4 (in case
> it is for this machine). In L4 you should find the
> wake_up of the wait_queue of the socket.
  
  thanks!
  
  In L4, wake_up should be fired  by IRQ event.
  where is the code for fire this callback ?

  

> 
> Regards,
> Rami Rosen
> http://ramirose.wix.com/ramirosen
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ