8139_tx_interrupt - Tx time

From: Adam Flizikowski (adam_fli_at_poczta.onet.pl)
Date: 10/10/03

  • Next message: Ingo Oeser: "Re: [PATCH] kfree_skb() bug in 2.4.22" 
    To: <linux-kernel@vger.kernel.org>
Date:	Fri, 10 Oct 2003 14:52:13 +0200

    Hi,

    I am trying to find out how long it takes to push packet off the NIC in
    8139_tx_interrupt(){} (kernel 2.4.20)

    but i don't know how to identify packet in this loop - i know that "entry"
    stands for the packet but in the loop underneath:
    /* code snippet for 8139_tx_interrupt(){}*/

    1726 while (tx_left > 0) {
    1727 int entry = dirty_tx % NUM_TX_DESC;
    1728 int txstatus;

    ...

    1762
    1763 dirty_tx++;
    1764 tx_left--; // <- is single packet sent just
    here??????
    1765 }

    what "tx_left" and "dirty_tx" variables stand for? Is single iteration
    through the loop (lines 1726-1765) related to SINGLE packet transmission?

    I wanted to put some probes inside tx_interrupt but not sure where it should
    start/stop measuring to show single packet transmission time.

    regards

    adam

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Ingo Oeser: "Re: [PATCH] kfree_skb() bug in 2.4.22"

    Relevant Pages

    • Re: Packet loss every 30.999 seconds
      ... Just to confirm the patch did not change the behavior. ... It looks like if you put the check at the top of the loop and the next node ... to increment if_ipackets but still lose the packet. ... not trigger the problem, but also be high enough to not significantly ...
      (freebsd-net)
    • Re: Packet loss every 30.999 seconds
      ... Just to confirm the patch did not change the behavior. ... It looks like if you put the check at the top of the loop and the next node ... to increment if_ipackets but still lose the packet. ... not trigger the problem, but also be high enough to not significantly ...
      (freebsd-stable)
    • Re: em network issues
      ... the count on every run through the loop. ... takes awhile until the int rolls over to 0. ... counting descriptors you could get all but the EOP descriptor of a packet ...
      (freebsd-net)
    • Re: sending a packet automatically
      ... i have a game which runs on an infinite loop as games do. ... updates are made to player movement and so forth. ... when i do it automatically due to the loop it can send the packet say 6 ... server ignore duplicate packets so they still get sent just nothing ...
      (microsoft.public.win32.programmer.networks)
    • Strange packet capture benchmark results
      ... I've been working on a new packet capture technique and I was comparing it to ... To test this I wrote a sender and a receiver application. ... loop for a configurable amount of time. ...
      (Linux-Kernel)