Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp5738534ybi; Wed, 31 Jul 2019 02:33:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzrJTPi86TltqxglmrmFUehvxvm4WP6uNMxBCbtuZA0w+sJ4D60IBLKN6wM3hyhxOheI6ZH X-Received: by 2002:a17:90a:3724:: with SMTP id u33mr1954500pjb.19.1564565616619; Wed, 31 Jul 2019 02:33:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564565616; cv=none; d=google.com; s=arc-20160816; b=RqAUVUyvuX4KhLc7aOFEK64UjNB7WnhrenOT/pZdXJIHpksfHBj6HMNXFh+ISkJjNV G+qzy/0SsPUza2+cGl0/rYDRRxafndoVxbXkIX1JGfz2zNS7WOOFFPg13OlzgcOV6zhi ZXeqkb72EXipUIDOslCIYCOb4P+1y71Cax3gULvB6+x+2E8R0ft6BapfgS25FqmblLJM Jl43n8j+CNw/EH+PTzGgENroVKynJwiKyU/reKvp3MayGIaI/YZfwV8y1OUUhwFdSMXV NR+C1i1ZehlObBZ7oENdI9CqJbr27Vr/8au93Mo3lSmzOmW7XlSHoFG4X0aJelBLmRCe HTsQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=GfAJ51CUeLmBmE4qHRxzRZoKP9enCqfeV2FsRC3d4Zw=; b=pr8YNqpc8K9/POydu/S8wT+ZDYrE4bZGDAbmeuMSL/npUCbErraX7LOnrMzvMLJeuy cTuLSDOyQMtBseA7I5mQ/RrJhEivlm8JRx++v0dSfNZO6m2THPWVgTFw6VoXkF66FbFh 5NibzEMGHdkehNpMeHtUG4shCIDRHsFwsKnvVUk0oZnbYYNlLyOXuBIBZ8/Lygv6iFnI gK7GYjjq1J+qvJH3ikVmVk/pOjjdrez8rJ3nAsCcyIyLDGN4sQKlSsevh5q7Q1/oBiBe gOsFlghTP69389wLDdvMFdE/bJ2rQrHPlfko7k6ZXTuQuWngf9/aO1X+b0/yy56kRbW9 BMag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h99si1062498pje.83.2019.07.31.02.33.21; Wed, 31 Jul 2019 02:33:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726941AbfGaJcT (ORCPT + 99 others); Wed, 31 Jul 2019 05:32:19 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:55570 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726651AbfGaJcT (ORCPT ); Wed, 31 Jul 2019 05:32:19 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hskxy-0004id-Ue; Wed, 31 Jul 2019 11:32:15 +0200 Message-ID: <3bb50da3442446a76f7ef59c4d53a7c349b87524.camel@sipsolutions.net> Subject: Re: [PATCHv6 5/9] nl80211: Add netlink attribute to configure TID specific tx rate From: Johannes Berg To: Tamizh chelvam , ath10k@lists.infradead.org Cc: linux-wireless@vger.kernel.org Date: Wed, 31 Jul 2019 11:32:14 +0200 In-Reply-To: <1560835632-17405-6-git-send-email-tamizhr@codeaurora.org> References: <1560835632-17405-1-git-send-email-tamizhr@codeaurora.org> <1560835632-17405-6-git-send-email-tamizhr@codeaurora.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org > /** > + * enum nl80211_tx_rate_setting - TX rate configuration type > + * @NL80211_TX_RATE_AUTOMATIC: automatically determine TX rate > + * @NL80211_TX_RATE_LIMITED: limit the TX rate by the TX rate parameter > + * @NL80211_TX_RATE_FIXED: fix TX rate to the TX rate parameter > + */ > +enum nl80211_tx_rate_setting { > + NL80211_TX_RATE_AUTOMATIC, > + NL80211_TX_RATE_LIMITED, > + NL80211_TX_RATE_FIXED, > +}; I'm not really quite sure how LIMITED it supposed to work? I mean, I could imagine all kinds of limits ... * limit to anything <= the given rate in kbps * limit to anything with long GI * limit to NSS <= given NSS * limit to MCS <= given MCS etc. I guess you could find a <= comparison for each dimension of the various parameters, and then if you don't want that particular one limited you give the maximum? Still not really clear to me how that should work. Also, would it be allowed to pass an invalid rate? Like something like "100Mbps legacy rate" when that's certainly not valid? You have no validation on this, so for LIMITED that might still seem useful (per my first bullet point above) but for anything else ... not so much? johannes