Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5415121yba; Wed, 10 Apr 2019 19:47:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqz+CTBw4orfctj0AoLTSrBPQuSthkFp0MIrIeI5Pj1zuUGNEzurjqg9QUapoPhP1kfVUyo+ X-Received: by 2002:a62:b40b:: with SMTP id h11mr47548066pfn.133.1554950865573; Wed, 10 Apr 2019 19:47:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554950865; cv=none; d=google.com; s=arc-20160816; b=olUxtGjDN0EphjVmk4SlmB42frEyvAmPpeSOCs2fQbN+XAKGMOB0mlzPg1vZMfC7/d bnoxfs4LsFGzdifrV4ewJFhpKV5k7xRZNfH73EWPT0plrTB4/DqlMuvYz9cayusWR4pA 2D+ULu5SaOkbtbifx6yrYO/0wMot+183Yb/gzRcO9ePD4IcGeJDhuXhRLAx63m6MMueK O0PwNQGbo+MTXBax+8CoV0jW69s0nykUgTT1TfI0sNO55gR4A9URwWlne2L2IRnXN3qx 5XdYSrBciW06Q0/aXDVNhJEtzLz3kAWWguife+RFvKD7k7jCHnXR6A/zyMzvvgNFtO6b lhug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=7J3Sb7foX/q2mIWrkS+UnpETZjYynVmELMHIRVZ7IY0=; b=s7ACLS3lUpcPmyoOV5hURNLHfBzLUJe8EDicoIf8AWHmWgP/+6Vn0SwENY8DlKXS9p ZlHkJXgZWUcGEeoNyFcLsffJ4vZtadoUQtjm++B6FLu5iBhQ5oEaQJG3D1ncGBHnhTim KBZje0D9m6MjnygrtiPNEWRuZ+AnntIOn3bqH1iDXhwzZ3SN0oaqUQeKOFXw8P+etXKE vDsGA6uN9LSWNg5ccbGlLbM2RzwGUKuHcTHfwvsOTrCEHZGluRkqd0euL3Z679sCH3hS P/Vamhb1gr1zJqEgJxDe35ThKeuspDLMUOBU3BNh//x5jiWaDeKYcIE7FI0ERqIcwLIw GMgA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 q1si33433779pfh.125.2019.04.10.19.47.29; Wed, 10 Apr 2019 19:47:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726757AbfDKCpd (ORCPT + 99 others); Wed, 10 Apr 2019 22:45:33 -0400 Received: from 178.115.242.59.static.drei.at ([178.115.242.59]:38146 "EHLO mail.osadl.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726106AbfDKCpd (ORCPT ); Wed, 10 Apr 2019 22:45:33 -0400 Received: by mail.osadl.at (Postfix, from userid 1001) id 025E35C2DC5; Thu, 11 Apr 2019 04:44:44 +0200 (CEST) Date: Thu, 11 Apr 2019 04:44:44 +0200 From: Nicholas Mc Guire To: Adham.Abozaeid@microchip.com Cc: hofrat@osadl.org, Ajay.Kathat@microchip.com, gregkh@linuxfoundation.org, linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC] staging: wilc1000: give usleep_range a range Message-ID: <20190411024444.GA5487@osadl.at> References: <1554552067-15421-1-git-send-email-hofrat@osadl.org> <20190409013656.GA22293@osadl.at> <0360e5c6-28c8-db9e-1e8d-80445fe433c0@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0360e5c6-28c8-db9e-1e8d-80445fe433c0@microchip.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 10, 2019 at 06:31:21PM +0000, Adham.Abozaeid@microchip.com wrote: > Hi Nicolas > > On 4/8/19 6:36 PM, Nicholas Mc Guire wrote: > > On Mon, Apr 08, 2019 at 09:10:00PM +0000, Adham.Abozaeid@microchip.com wrote: > >> Hi Nicholas > >> > >> On 4/6/19 5:01 AM, Nicholas Mc Guire wrote: > >>> External E-Mail > >>> > >>> > >>> Someone that knows the motivation for setting the time to 2 millisecond > >>> might need to check if the 2 milliseconds where seen as tollerable max or > >>> min - I'm assuming it was the min so extending. > >> 2 msec is the time the chip takes to wake up from sleep. > >> > >> Increasing the maximum to 5 msec will impact the throughput since this call is on the transmit path. > >> > > ok - would it be tollerable to make it 2 - 2.5 ms ? > > even that would allow for the hrtimer subsystem to optimize > > a lot. In any case the min==max case gives you very little > > if you run a test-case with usleep_range(1000,1000) and > > a loop with usleep_range(1000,2000) and look at the distribution > > you will have a hard time seeing any difference. > > yes, I believe 2.5 shouldn't be a problem. > thanks - will send out a V2 then shortly. thx! hofrat