From: "John W. Linville" <linville@tuxdriver.com>
To: Gottfried Haider <gottfried.haider@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce: odd ping behavior
Date: Wed, 6 Apr 2011 10:57:00 -0400 [thread overview]
Message-ID: <20110406145700.GC11941@tuxdriver.com> (raw)
In-Reply-To: <BANLkTi=ueo0Vm5VPRh=LMCQ-huGzXMyvFQ@mail.gmail.com>
On Wed, Apr 06, 2011 at 02:37:27AM +0200, Gottfried Haider wrote:
> Thanks for testing. I had hoped that the ping results could make a
> light go on somewhere..
FWIW, the behaviour you described sounds a lot like bufferbloat.
http://bufferbloat.net
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-04-06 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 14:33 rtl8192ce: odd ping behavior Gottfried Haider
2011-04-05 17:42 ` Larry Finger
2011-04-06 0:37 ` Gottfried Haider
2011-04-06 14:57 ` John W. Linville [this message]
2011-04-06 15:05 ` Gottfried Haider
2011-04-06 15:39 ` John W. Linville
2011-04-06 16:10 ` Larry Finger
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=20110406145700.GC11941@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gottfried.haider@gmail.com \
--cc=linux-wireless@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).