netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <info@lategoodbye.de>
To: netdev@vger.kernel.org
Cc: arnd@arndb.de
Subject: Packet loss when txqueuelen is zero
Date: Sat, 28 Jun 2014 12:59:27 +0200	[thread overview]
Message-ID: <53AEA00F.6060500@lategoodbye.de> (raw)

Hi,

i'm new to Linux network driver development and currently i want to port 
the QCA7000 network driver to mainline [1]. I concentrate my tests on tx 
buffering since my last QCA7000 patch RFC [2]. Now i've found a test 
scenario which leads to packet loss:

host A          Powerline       host B
(QCA7000)       Ethernet        Ethernet
192.168.1.3     adaptor         192.168.1.5
|------------------|---------------|
      Homeplug         Ethernet
      10 Mbit          100 Mbit

1. Reduce the txqueuelen from 100 (default value) to 0
2. Run ping in flood mode on host A to host B

ping -c 200 -s 10000 -f 192.168.1.5

3. ping reports a high packet loss

Additional information:
- QCA7000 network driver has a tx ring size of 10 packets
- the packet loss doesn't appear when txqueuelen is 100

Here are my questions:

Is the packet loss a expected result for this scenario?
If not what could be the cause of the packet loss?

[1] - https://github.com/I2SE/qca7000/tree/linux-mainline
[2] - http://www.spinics.net/lists/netdev/msg280751.html

             reply	other threads:[~2014-06-28 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 10:59 Stefan Wahren [this message]
2014-06-28 14:40 ` Packet loss when txqueuelen is zero Eric Dumazet
2014-06-29 13:51   ` Stefan Wahren
2014-06-30  5:49     ` Eric Dumazet
2014-06-30 17:08       ` Stefan Wahren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53AEA00F.6060500@lategoodbye.de \
    --to=info@lategoodbye.de \
    --cc=arnd@arndb.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).