Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Dave Taht <dave.taht@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	bloat-devel@lists.bufferbloat.net
Cc: linux-wireless@vger.kernel.org
Subject: Recommend a Wireless/WiFi chip, that best address bufferbloat
Date: Tue, 8 Oct 2013 11:57:58 +0200	[thread overview]
Message-ID: <20131008115758.694477b7@redhat.com> (raw)

Hi All,

As Dave Taht repeats, we have not solved bufferbloat on Wifi, yet.

I've been approached by some embedded developers, who need to choose
some Wifi hardware for their device, and is concerned about bufferbloat.

What do we recommend of Wifi chips?
- Which ones are the least-bad regrading bufferbloat?
- Which ones do we hope to solve in the near-future?

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer

                 reply	other threads:[~2013-10-08  9:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131008115758.694477b7@redhat.com \
    --to=brouer@redhat.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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