From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] vdso: Add comment about reason for vdso struct ordering
Date: Mon, 1 Jul 2024 17:17:59 +0100 [thread overview]
Message-ID: <f98d7d30-ea54-4f46-9052-9027a4580d87@arm.com> (raw)
In-Reply-To: <87jzi5p1qs.fsf@somnus>
On 01/07/2024 16:31, Anna-Maria Behnsen wrote:
> Vincenzo Frascino <vincenzo.frascino@arm.com> writes:
>
>> On 01/07/2024 15:47, Anna-Maria Behnsen wrote:
>>> Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
>>
>> nit: Can you please add something in the commit message?
>
> Sure, I would propose the following:
>
> The struct vdso_data is optimized for fast access to the often required
> struct members. The optimization is not documented in the struct
> description but it should be kept in mind, when working with the
> vdso_data struct.
>
> Add a comment to the struct description.
>
>>
>> Otherwise:
>>
>> Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
>
> Thanks!
>
Works for me. Thanks!
>>> ---
>>> include/vdso/datapage.h | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/include/vdso/datapage.h b/include/vdso/datapage.h
>>> index d04d394db064..7647e0946f50 100644
>>> --- a/include/vdso/datapage.h
>>> +++ b/include/vdso/datapage.h
>>> @@ -77,6 +77,10 @@ struct vdso_timestamp {
>>> * vdso_data will be accessed by 64 bit and compat code at the same time
>>> * so we should be careful before modifying this structure.
>>> *
>>> + * The ordering of the struct members is optimized to have fast access to the
>>> + * often required struct members which are related to CLOCK_REALTIME and
>>> + * CLOCK_MONOTONIC. This information is stored in the first cache lines.
>>> + *
>>> * @basetime is used to store the base time for the system wide time getter
>>> * VVAR page.
>>> *
>>>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2024-07-01 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 14:47 [PATCH 0/5] vdso (generic and x86): Misc minor cleanups Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 1/5] vdso/gettimeofday: Clarify comment about open coded function Anna-Maria Behnsen
2024-07-01 14:58 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 2/5] vdso: Add comment about reason for vdso struct ordering Anna-Maria Behnsen
2024-07-01 15:10 ` Vincenzo Frascino
2024-07-01 15:31 ` Anna-Maria Behnsen
2024-07-01 16:17 ` Vincenzo Frascino [this message]
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 3/5] x86/vdso: Fix function reference in comment Anna-Maria Behnsen
2024-07-01 15:11 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 4/5] x86/vgtod: Remove unused typedef gtod_long_t Anna-Maria Behnsen
2024-07-01 15:19 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
2024-07-01 14:47 ` [PATCH 5/5] x86/vdso: Remove unused include Anna-Maria Behnsen
2024-07-01 16:19 ` Vincenzo Frascino
2024-07-03 19:36 ` [tip: timers/core] " tip-bot2 for Anna-Maria Behnsen
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=f98d7d30-ea54-4f46-9052-9027a4580d87@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=anna-maria@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®