From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by huchra.bufferbloat.net (Postfix) with ESMTP id 8A76821F1C4 for ; Tue, 8 Oct 2013 02:58:09 -0700 (PDT) Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r989w78E014074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 8 Oct 2013 05:58:07 -0400 Received: from localhost (ovpn-116-70.ams2.redhat.com [10.36.116.70]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r989w4j3032461; Tue, 8 Oct 2013 05:58:04 -0400 Date: Tue, 8 Oct 2013 11:57:58 +0200 From: Jesper Dangaard Brouer To: Dave Taht , John Linville , bloat-devel@lists.bufferbloat.net Subject: Recommend a Wireless/WiFi chip, that best address bufferbloat Message-ID: <20131008115758.694477b7@redhat.com> Organization: Red Hat Inc. Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.25 Cc: linux-wireless@vger.kernel.org X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 09:58:09 -0000 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