From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: <netfilter-devel@vger.kernel.org>, <coreteam@netfilter.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-s390@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <linux-scsi@vger.kernel.org>,
<xen-devel@lists.xenproject.org>, <linux-block@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <ath11k@lists.infradead.org>,
<linux-mm@kvack.org>, <linux-bluetooth@vger.kernel.org>,
<linux-staging@lists.linux.dev>, <ceph-devel@vger.kernel.org>,
<live-patching@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<etnaviv@lists.freedesktop.org>, <oss-drivers@corigine.com>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 00/21] Converge on using secs_to_jiffies()
Date: Mon, 9 Dec 2024 16:03:31 +0100 [thread overview]
Message-ID: <3113d4f4-4f8b-41d6-af89-f82cbc89da75@intel.com> (raw)
In-Reply-To: <95a461ca-3ed6-4380-ad1a-da12e1109675@csgroup.eu>
On 12/9/24 1:45 PM, Christophe Leroy wrote:
>
>
> Le 09/12/2024 à 13:01, Przemek Kitszel a écrit :
>> On 12/6/24 9:58 PM, Easwar Hariharan wrote:
>>> On 11/29/2024 4:57 AM, Przemek Kitszel wrote:
>>>>
>>>> [removed most non-list recipients, it's just too much]
>>>>
>>>> On 11/15/24 10:26 PM, Easwar Hariharan wrote:
>>> <snip>
>>
>>>>
>>>> Regarding code - you could also convert msecs_to_jiffies(const * HZ),
>>>> there are 10 that are greppable.
Thanks to Christope, I re-examined those ~10 cases, and that should be
refactored by just dropping msec_to_jiffies() part, not replacing
by sec_to_jiffies().
>>>>
>>>
>>> Those seem to be mistakes. const*HZ is a seconds-denominated timeout,
>>> being passed to msecs_to_jiffies() which will treat it as a
>>> millisecond-denominated timeout resulting in an excessively long
>>> timeout. I suppose that's better than a too-short timeout, and
>>> apparently it's been working fine all along since hardware responds
>>> before the too-long timeout expires. Half of them are in
>>> drivers/scsi/arcmsr/arcmsr_hba.c and the pattern has apparently been
>>> there since 2010.
>>
>> my point was that, the default value of HZ is 1000, and most of the code
>> that is just `$value*HZ` was meant as "$value seconds, in ms unit".
>
> I can't follow you here. The default value of HZ is 250 as far as I can
> see.
as default I understand "the value that is effective for those that
don't tweak", not necessarily "the fallback that will be used when not
set by any other means". On my RedHat and Fedora boxes it's 1000.
>
> Regardless, HZ is the number of jiffies per second, nothing else.
That is true. But the name is wrong.
>
>>
>> Same for HZ/const, HZ/2 being 500ms.
>>
>> HZ is awful in that it is not 1s but 1/s, but it was easy to abuse the
>> value in simple context.
>
> Why is that awful ?
so, 1Hertz = 1/1s == once per second,
something happening twice per second, with freq of 2Hz, repeats
each HZ/2 jiffies
https://en.wikipedia.org/wiki/Hertz
the #define name should be really JHZ -> JIFFIES_PER_SECOND
>
> HZ is a nice macro that gives you the number of ticks per second, so
> that you are able to easily calculate the number of ticks for a given
> duration, regardless of the configured number of ticks per second.
Again, technically true, but default being eq to number of msec in sec,
causes it to bite.
prev parent reply other threads:[~2024-12-09 15:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 21:26 Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 01/21] netfilter: conntrack: Cleanup timeout definitions Easwar Hariharan
2024-11-15 22:34 ` Stephen Rothwell
2024-11-16 0:13 ` Easwar Hariharan
2024-11-16 9:40 ` Christophe Leroy
2024-11-18 18:13 ` Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 02/21] coccinelle: misc: Add secs_to_jiffies script Easwar Hariharan
2024-11-16 6:05 ` Christophe JAILLET
2024-11-18 18:09 ` Easwar Hariharan
2024-11-16 9:52 ` Christophe Leroy
2024-11-18 18:14 ` Easwar Hariharan
2024-11-16 10:23 ` [cocci] " Markus Elfring
2024-11-15 21:26 ` [PATCH v2 03/21] arm: pxa: Convert timeouts to use secs_to_jiffies() Easwar Hariharan
2024-11-16 10:26 ` Christophe Leroy
2024-11-15 21:26 ` [PATCH v2 04/21] s390: kernel: " Easwar Hariharan
2024-11-18 8:26 ` Heiko Carstens
2024-11-15 21:26 ` [PATCH v2 05/21] powerpc/papr_scm: Convert timeouts to secs_to_jiffies() Easwar Hariharan
2024-11-16 10:06 ` Christophe Leroy
2024-11-16 10:40 ` Dan Carpenter
2024-11-16 11:24 ` Julia Lawall
2024-11-15 21:26 ` [PATCH v2 06/21] mm: kmemleak: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 07/21] accel/habanalabs: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 08/21] drm/xe: Convert timeout " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 09/21] drm/etnaviv: Convert timeouts " Easwar Hariharan
2024-12-02 21:16 ` Christian Gmeiner
2024-11-15 21:26 ` [PATCH v2 10/21] scsi: lpfc: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 11/21] scsi: arcmsr: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 12/21] scsi: pm8001: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 13/21] xen/blkback: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 14/21] gve: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 15/21] wifi: ath11k: " Easwar Hariharan
2024-11-15 22:59 ` Jeff Johnson
2024-11-15 21:26 ` [PATCH v2 16/21] Bluetooth: MGMT: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 17/21] staging: vc04_services: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 18/21] ceph: " Easwar Hariharan
2024-11-28 12:28 ` Alex Markuze
2024-11-15 21:26 ` [PATCH v2 19/21] livepatch: " Easwar Hariharan
2024-11-16 10:10 ` Christophe Leroy
2024-11-18 11:06 ` Petr Mladek
2024-11-18 18:18 ` Easwar Hariharan
2024-11-19 1:43 ` zhang warden
2024-11-19 8:52 ` Petr Mladek
2024-11-19 9:09 ` Miroslav Benes
2024-11-15 21:26 ` [PATCH v2 20/21] ALSA: line6: " Easwar Hariharan
2024-11-15 21:26 ` [PATCH v2 21/21] nfp: " Easwar Hariharan
2024-11-16 10:13 ` Christophe Leroy
2024-11-15 21:29 ` [PATCH v2 00/21] Converge on using secs_to_jiffies() Easwar Hariharan
2024-11-15 21:41 ` Jeff Johnson
2024-11-15 22:15 ` Easwar Hariharan
2024-11-15 23:20 ` Thomas Gleixner
2024-11-16 7:46 ` Christophe Leroy
2024-11-16 10:16 ` Christophe Leroy
2024-11-16 10:23 ` LEROY Christophe
2024-11-18 18:07 ` Easwar Hariharan
2024-11-29 12:57 ` Przemek Kitszel
2024-12-06 20:58 ` Easwar Hariharan
2024-12-09 12:01 ` Przemek Kitszel
2024-12-09 12:45 ` Christophe Leroy
2024-12-09 15:03 ` Przemek Kitszel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3113d4f4-4f8b-41d6-af89-f82cbc89da75@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=ath11k@lists.infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=coreteam@netfilter.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eahariha@linux.microsoft.com \
--cc=etnaviv@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox