From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 0CA7421F185 for ; Thu, 11 Jul 2013 10:09:43 -0700 (PDT) Received: by mail-ie0-f180.google.com with SMTP id f4so17732524iea.25 for ; Thu, 11 Jul 2013 10:09:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lszeGUMUkJM9LVCVbt43CLN/7A+788tIiqQ23cJgHx4=; b=HQFIw7Agz7jRyUTRchpyz1wtN226jMeDyTyoqFtqCSozKbmZ4M4r1ZXuJxVblyDyQz SRHXeY6IdxQ5gc0S8SFTP8KFueguXypSzmu0FlcDNG7pgGF22l8xgurpdl9osOLVqdlP 1LAxNRlUmJCHXW3RAvaJJ2uNY8O2XdxE868kr5ErwdL2f9KLYCp54M0h92vdngHD5eHU JzgBuJaa8ktqZrBTWBz25aP7uxN/+8bufV19TvaOFq1rJSZ0mX7mL0fMKGmZe8eaiuGR yXsZmjbmyhalHKltmwVuCknWGovBGkEMgwhlsILNQPwT1VYcMNZqqyU9CBWYIhWzdXem eC4g== MIME-Version: 1.0 X-Received: by 10.42.37.203 with SMTP id z11mr11572033icd.56.1373562582457; Thu, 11 Jul 2013 10:09:42 -0700 (PDT) Received: by 10.64.98.162 with HTTP; Thu, 11 Jul 2013 10:09:42 -0700 (PDT) Date: Thu, 11 Jul 2013 10:09:42 -0700 Message-ID: From: Dave Taht To: codel@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Codel] hardware multiqueue in fq_codel? X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 17:09:43 -0000 In my default environments (wifi, mainly) the hardware queues have very different properties. I'm under the impression that in at least a few ethernet devices they are essentially the same. That said, in the sch_mq case, an entirely separate qdisc is created per hardware queue, and it's always been puzzling to me as to how to attempt to use them within a single qdisc in the pull-through manner. logically, you should be able to take the fq_codel hash index (idx % dev->num_tx_queues) and spread out across the hardware queues that way, but I have no idea where that info would go (the skb? the flow?) or even if it were possible as per the pull through problem... (This does not mean that I necessarily think hardware multiqueues are a good idea... (certainly the results I get out of 802.11e are terrible - but it would be nice to have a unified solution for hw multiqueue devices) --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html