From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 14 Apr 2014 20:00:08 +0200 From: Bastian Bittorf Message-ID: <20140414180008.GW26376@medion.lan> References: <1397484205-20905-1-git-send-email-antonio@meshcoding.com> <1397484205-20905-2-git-send-email-antonio@meshcoding.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1397484205-20905-2-git-send-email-antonio@meshcoding.com> Subject: Re: [B.A.T.M.A.N.] [PATCH 2/7] mac80211: add get_expected_throughput API Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Cc: devel@lists.open80211s.org, Johannes Berg , linux-wireless@vger.kernel.org, Antonio Quartulli * Antonio Quartulli [14.04.2014 16:53]: > From: Antonio Quartulli > > Add get_expected_throughput() API to mac80211 so that each > driver can implement its own version based on the RC Without understanding this fully: thank you. What is not clear to me: the function returns Mbps/100. Why not simply kilobit/second? Also: does it return expected_goodput or "only" throughput? Because we want to use this value not internally only it should reflect the real usecase (and should also be human-readable). For a meshnet it is important to know, that a 10mbit ethernet line is faster than a 60 mbit wireless link with a low tx-probability. bye, Bastian Bittorf