Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2485852ybd; Mon, 24 Jun 2019 07:15:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqz2Bpjzlkqtjl+W4V8AnFbtmvagNARmVHGWsM9ylI3udFxL/nVisCvpJExozFkeOUJEtpdt X-Received: by 2002:a63:f746:: with SMTP id f6mr9583680pgk.56.1561385737233; Mon, 24 Jun 2019 07:15:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561385737; cv=none; d=google.com; s=arc-20160816; b=swiFLYLDme3F8mYQDLfUaP6xtfH5tbboDsq5eiiO4akWYc8jdGxLCV9Lp3OBJ+yWQG 0PuGB1FI/5IjP27OIrxwFFuezqv4d3bXA/IDZV9l8UDBzjIGuiCpvVpjD6q5MdMplVGY nC2NArlv/OInjWULBDRIVIHjzMtO1JVVuC/Ei+IFrCsudUztHtfcVN7OM4uWwt6srg0U reWXy5B56c4eSeYY1h4oBJbRMlBuxAHhX5VgzSpw/X2+pYKut56LvCFRWmKG19wggMPO gpbbAmT+JkJp7gE+6GlHw/suGRuJhARB3z2NZblQG4YpVnONgxeihVQqDqExpl1jnT71 dz8A== 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:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=RRMTsQrOVxnGsJwHXWfRxav1UvwRYG+Hvce0t/skUOI=; b=lGJKaEcsOqGfHcqc4JOHNv0+c70GRqqPuYjQf+kKS03MVv0d9K9mJmgRp/R2en6Qp1 UDnxg3pzj1CeIRUGYiHqrefFH0NDdp/3OPzJIzW9BxjntcPY+Ij1wocJ/5JW/GvMP0Oh foRRQtpeBCfmRm8HoocJ/lO/mesGwq6ogoRA63FcVOc3JSJ8OHeSTuFUr7WiPaSL92fA d1jLeVECxV8+IUQQATVmO/I+l3dnEobByd3Q5pvKvHJgE7hOjprJ3oqzsLUrXTU7z9/k J0s5E6wSZW5KKFa9aS4AaDttpKIWtNbBwLkMtx+Tp8gfBYS8oubB+kKs0TdGX63GqYtr oJZQ== 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 gn14si7860641plb.395.2019.06.24.07.15.20; Mon, 24 Jun 2019 07:15:37 -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 S1731191AbfFXNdt (ORCPT + 99 others); Mon, 24 Jun 2019 09:33:49 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:19066 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728884AbfFXNdt (ORCPT ); Mon, 24 Jun 2019 09:33:49 -0400 Received: from DGGEMS402-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id D7DD23998DC962976001; Mon, 24 Jun 2019 21:33:43 +0800 (CST) Received: from [127.0.0.1] (10.184.225.177) by DGGEMS402-HUB.china.huawei.com (10.3.19.202) with Microsoft SMTP Server id 14.3.439.0; Mon, 24 Jun 2019 21:33:37 +0800 Subject: Re: [PATCH next] softirq: enable MAX_SOFTIRQ_TIME tuning with sysctl max_softirq_time_usecs To: Thomas Gleixner CC: , , Kees Cook , , , , , , , , , , , , , "wangxiaogang (F)" , "Zhoukang (A)" , Mingfangsen , , Eric Dumazet References: <0099726a-ead3-bdbe-4c66-c8adc9a4f11b@huawei.com> From: Zhiqiang Liu Message-ID: Date: Mon, 24 Jun 2019 21:32:48 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="gbk" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.184.225.177] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/6/24 17:45, Thomas Gleixner wrote: > Zhiqiang, > > On Mon, 24 Jun 2019, Zhiqiang Liu wrote: >> ?? 2019/6/24 0:38, Thomas Gleixner ะด??: >> >> Thanks again for your detailed advice. >> As your said, the max_softirq_time_usecs setting without explaining the >> relationship with CONFIG_HZ will give a false sense of controlability. And >> the time accuracy of jiffies will result in a certain difference between the >> max_softirq_time_usecs set value and the actual value, which is in one jiffies >> range. >> >> I will add these infomation in the sysctl documentation and changelog in v2 patch. > > Please make the sysctl milliseconds based. That's the closest approximation > of useful units for this. This still has the same issues as explained > before but it's not off by 3 orders of magitude anymore. > > Thanks, > > tglx > Thanks for your suggestion. I will adopt max_softirq_time_ms to replace MAX_SOFTIRQ_TIME in v2.