public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stefan Wahren <info@lategoodbye•de>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: netdev@vger•kernel.org, arnd@arndb•de
Subject: Re: Packet loss when txqueuelen is zero
Date: Sun, 29 Jun 2014 15:51:33 +0200	[thread overview]
Message-ID: <53B019E5.4060905@lategoodbye.de> (raw)
In-Reply-To: <1403966418.15139.27.camel@edumazet-glaptop2.roam.corp.google.com>

Am 28.06.2014 16:40, schrieb Eric Dumazet:
>>
>> Is the packet loss a expected result for this scenario?
>
> Sure it is totally expected.
>
> -f is a flood ping, and you remove ability to store packets in the Qdisc
> (pifo_fast limit is device txqueuelen).
>
> If you have txqueuelen = 100, then the socket used by ping will more
> likely hit its SO_SNDBUF limit and ping will handle this properly (it
> detects that a sendmsg() returns -1, errno = ENOBUF
>
> If QCA7000 network driver has a tx ring size of 10 packets, you really
> want a qdisc being able to store bursts.

Thanks for your explanation. So it's not a network driver bug.

>
> If bufferbloat is your concern, you can switch pfifo_fast to fq_codel or
> fq
>
> tc qdisc replace dev eth0 root fq_codel  (or fq to get TCP pacing)
>

But fq_codel requires BQL in the QCA7000 network driver. Right?

next prev parent reply	other threads:[~2014-06-29 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 10:59 Packet loss when txqueuelen is zero Stefan Wahren
2014-06-28 14:40 ` Eric Dumazet
2014-06-29 13:51   ` Stefan Wahren [this message]
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=53B019E5.4060905@lategoodbye.de \
    --to=info@lategoodbye$(echo .)de \
    --cc=arnd@arndb$(echo .)de \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox