WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Understanding netback packet transmission code

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Understanding netback packet transmission code
From: Micky Kay <weirdbluelights@xxxxxxxxx>
Date: Tue, 27 Oct 2009 11:47:44 -0400
Delivery-date: Tue, 27 Oct 2009 08:48:08 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=ubzJY93Zc/Ik5uD8+HQzxmq2TQWYLvn+L3Pxc3A4jc0=; b=XjN627MA+ujiQFTjHDAhH/B8DrGYgyfsUerzAzmNAH5LqLKXvHocDvmjUhP8KH2SCu w5qDrwgzx06rklfRZdc03s/LYyJlsgg4CzNoK55QpXXGm0GOZdem0GNbAUVbHm/L5JSY vN7N4aC0e4kItapWjag8xUr0Dl3l5TQQ5LC8I=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>