[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56CFF561.4050805@miraclelinux.com>
Date: Fri, 26 Feb 2016 15:49:05 +0900
From: YOSHIFUJI Hideaki/吉藤英明
<hideaki.yoshifuji@...aclelinux.com>
To: Deepa Dinamani <deepa.kernel@...il.com>
Cc: hideaki.yoshifuji@...aclelinux.com,
Linux Network Devel Mailing List <netdev@...r.kernel.org>,
y2038@...ts.linaro.org, Arnd Bergmann <arnd@...db.de>,
John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH 1/4] kernel: time: Add current_nw_timestamp() for network
timestamps
Hi,
Deepa Dinamani wrote:
>>> include/linux/ip.h | 2 ++
>>> include/linux/time64.h | 3 +++
>>> kernel/time/time.c | 26 ++++++++++++++++++++++++++
>>> 3 files changed, 31 insertions(+)
>>>
>> Since net/ipv4/* are the only users, it is enough to put
>> it in under net/ipv4/.
>
> time.c hosts functions that are used by individual subsystems like
> current_fs_time() used by filesystems
> (sometimes used by other subsystems also).
>
> The network timestamp function is used for both source route ip option
> and timestamp icmp messages.
> So it makes it difficult for it to be owned by a single layer.
> This is the reason it was chosen to include here.
>
> Another option is to include it in the lowest layer its used:
> af_inet.c. Is this what you were suggesting?
>
Yes, that's right.
--yoshfuji
> -Deepa
>
Powered by blists - more mailing lists