From: Heena Sirwani <heenasirwani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: opw-kernel-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: arnd-r2nGTMty4D4@public.gmane.org,
lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v5 0/2] cpuset: Replace instances of time_t with time64_t to solve y2038 problem
Date: Mon, 13 Oct 2014 10:19:51 +0530 [thread overview]
Message-ID: <cover.1413174804.git.heenasirwani@gmail.com> (raw)
The following patchset replaces instances of time_t with time64_t to
address the y2038 problem. The patchset also makes the code independent
of settimeofday().
Changes in v2:
- Changed the function get_seconds() that return a 32-bit
integer to ktime_get_real_ts64() that returns a struct of
type timespec64 and use the tv_sec part which is 64-bit.
- Change the type of ticks from time_t to u32. We keep ticks as
32-bits as the function uses 32-bit arithmetic which would
prove less expensive than 64-bit arithmetic and the function
is expected to be called atleast once every 32 seconds.
Changes in v3:
- Changed commenting style.
Changes in v4:
- Changed the subject tag.
Changes in v5:
- Changed a comment and added a patch that make the code
independent of settimeofday().
Heena Sirwani (2):
cpuset: Replace all instances of time_t with time64_t
cpuset: Replace ktime_get_real_ts64() with ktime_get_ts64()
kernel/cpuset.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-13 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 4:49 Heena Sirwani [this message]
[not found] ` <cover.1413174804.git.heenasirwani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-13 4:51 ` [PATCH v5 1/2] cpuset: Replace all instances of time_t with time64_t Heena Sirwani
2014-10-13 4:52 ` [PATCH v5 2/2] cpuset: Replace ktime_get_real_ts64() with ktime_get_ts64() Heena Sirwani
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=cover.1413174804.git.heenasirwani@gmail.com \
--to=heenasirwani-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=opw-kernel-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).