From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: Can iperf work with no qos? (TCP mode)
Date: Sat, 11 Jun 2011 19:57:21 +0200 [thread overview]
Message-ID: <20110611195721.735dcf4c@maggie> (raw)
In-Reply-To: <BANLkTimaUBe6kszbvSeSPTXR6m1t8C8O-A@mail.gmail.com>
On Sat, 11 Jun 2011 19:47:31 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> I can not get any results when trying to use iperf in TCP mode with
> driver not supporting qos.
>
> Is this expected? Does iperf fill connection with so many packets,
> it's not possible to get response from the iperf receiver? Should not
> Linux somehow schedule packet to allow bi-direction communication,
> even on really filled connection?
iperf will only fill the best effort queue. At least that's what it did
last time when I looked into the code.
You can verify that with b43's ring statistics.
next prev parent reply other threads:[~2011-06-11 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 17:47 Can iperf work with no qos? (TCP mode) Rafał Miłecki
2011-06-11 17:57 ` Michael Büsch [this message]
2011-06-11 18:05 ` Rafał Miłecki
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=20110611195721.735dcf4c@maggie \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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