From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id E4B6E3B25E for ; Wed, 10 Aug 2016 11:27:18 -0400 (EDT) Received: by mail-wm0-x22a.google.com with SMTP id f65so97243847wmi.0 for ; Wed, 10 Aug 2016 08:27:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=O9KrPw6NXq5WK8DIp4S6+f1J4MeJjhfiY7r95xhLti4=; b=slfyiSNGIuPLt7su4EYzIZxhWir9HMO7UIX9OZxTDrBEiP1Mk21wCghyPlr/9bhDe0 dN/vEabulbWpLcbyjL6WMRZ0+xzUW+HrcGCORBJGgSPCF6j/26KcNyWlVv4scaF3gGds ctzkKJzvFIjV3OuEHT//kzQdgg1jSL2zNgTLk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=O9KrPw6NXq5WK8DIp4S6+f1J4MeJjhfiY7r95xhLti4=; b=EdconkAzEADDX2B9yHR6p6Ch2BFyxN1TYp68Df//YHfSPygr4dF97lAa6ysrNShaR3 Z8u9wkaMgJEv72WoDRs17U+NMOZcxdPk1ycO0wjKSP3KtbUq/c9jCV7Rnm030kf6TstM H8DIpQdSeT9zlE796XibaUG3ROHzJAJY+4u1uAkc3CeIIwT+EBh7z6fekW4ITFbipzlJ lSqlaFK0qCQfSQs8kw3Q3DuEh8C/P3kntdP4VwO++Z/gfZ3MYg+nAT/xlfeUrT1blXWH 6pBpCZ77sQePuk5vL59lv2BujCf7pi5UeHq/9WfgwxR+yVP5iAhDjWp0vuZg7ZO0QooH 44Gw== X-Gm-Message-State: AEkoouuLswCNFJoz3F6LqZwEw3Cy+7XuaWC7AhZoqoLskm9BiSPN9vOEPKiUNVDE/yCKzTHY15HH2+TbCb7nieNOXhCoJ19J+UmPUm0+0IYY4IbfYxTdwWbQuu975aM1LzPmThLc2gGB9CmXIRhq7HDWbSOGbXhsMzzn/w== X-Received: by 10.28.139.144 with SMTP id n138mr3988024wmd.71.1470842837280; Wed, 10 Aug 2016 08:27:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.146.134 with HTTP; Wed, 10 Aug 2016 08:27:16 -0700 (PDT) In-Reply-To: <8760r8bwxm.fsf@toke.dk> References: <8760r8bwxm.fsf@toke.dk> From: Michal Kazior Date: Wed, 10 Aug 2016 17:27:16 +0200 Message-ID: To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Cc: make-wifi-fast@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-DomainID: tieto.com Subject: Re: [Make-wifi-fast] Carrying the CoDel timestamp into the driver X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2016 15:27:19 -0000 On 10 August 2016 at 15:00, Toke H=C3=B8iland-J=C3=B8rgensen = wrote: > Hi Michal > > In your mac80211 FQ-CoDel patch, you put the CoDel timestamp into a > union with the vif pointer in struct ieee80211_tx_info. This means the > timestamp is not available in the driver. I'm experimenting with some > changes where having the enqueue time available would be useful. > > Do you have any good ideas as to where else we could store the enqueue > time somewhere the driver can retrieve it? I did explore this idea for different purposes though - to maintain per-packet expected_duration. I think it should be in the linux-wireless archives. It compacted band, ack_frame_id I think but you get limited number of *bits*. .. or you could remove the rate control stuff from tx_info and convert all drivers to use mac80211 API to fetch it per-station on-demand only I guess.. Micha=C5=82