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

[Xen-devel] Understanding netback packet transmission code

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Micky Kay <weirdbluelights@xxxxxxxxx>
  • Date: Tue, 27 Oct 2009 11:47:44 -0400
  • Delivery-date: Tue, 27 Oct 2009 08:48:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iFlFHa66Ft9y+RLC6hk2yc81pfVWl31pEWGW9JhP8OBIYbMUyPU99jVKwsUwmtneg5 FBmoBVmjlVpKTwfbJ7P25eN9/RZlA11QA+XLcFLHvLHilXqHCgYqDPz+EHTv+eWwCbGF dF+01ZriOWk/ylmBE0Mj9utlN79vwXLoI04Qw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I figured that the net_tx_action function is the one that schedules packet transmission. I understood a fair portion of the code but for the call to netif_rx (netback.c:1454) after scheduling the tx_response and the update of the rx stats in the transmission function. I also noticed that netif_be_start_xmit function queues the sk_buff passed to it in the receive queue (rx_queue) and schedules the net_rx_tasklet (netback.c:336).

Could someone demystify all of this please? Thanks much.

- Micky
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.