[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bk02wawy.ffs@tglx>
Date: Wed, 02 Oct 2024 21:40:45 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, FUJITA Tomonori
<fujita.tomonori@...il.com>
Cc: aliceryhl@...gle.com, andrew@...n.ch, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, hkallweit1@...il.com, tmgross@...ch.edu,
ojeda@...nel.org, alex.gaynor@...il.com, gary@...yguo.net,
bjorn3_gh@...tonmail.com, benno.lossin@...ton.me, a.hindborg@...sung.com
Subject: Re: [PATCH net-next v1 1/2] rust: add delay abstraction
On Wed, Oct 02 2024 at 16:52, Miguel Ojeda wrote:
> On Wed, Oct 2, 2024 at 4:40 PM FUJITA Tomonori
> <fujita.tomonori@...il.com> wrote:
>>
>> Sure. Some code use ktime_t to represent duration so using Ktime for
>> the delay functions makes sense. I'll add some methods to Ktime and
>> use it.
>
> We really should still use different types to represent points and
> deltas, even if internally they happen to end up using/being the
> "same" thing.
>
> If we start mixing those two up, then it will be harder to unravel later.
>
> I think Thomas also wanted to have two types, please see this thread:
> https://lore.kernel.org/rust-for-linux/87h6vfnh0f.ffs@tglx/ (we also
> discussed clocks).
Correct. They are distinct.
Btw, why is this sent to netdev and not to LKML? delay is generic code
and has nothing to do with networking.
Thanks,
tglx
Powered by blists - more mailing lists