LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org> To: Arnd Bergmann <arnd@arndb.de> Cc: y2038 Mailman List <y2038@lists.linaro.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, the arch/x86 maintainers <x86@kernel.org>, Linux API <linux-api@vger.kernel.org>, linux-arch <linux-arch@vger.kernel.org>, Paul Eggert <eggert@cs.ucla.edu>, "Eric W . Biederman" <ebiederm@xmission.com>, Richard Henderson <rth@twiddle.net>, Ivan Kokshaysky <ink@jurassic.park.msu.ru>, Matt Turner <mattst88@gmail.com>, Al Viro <viro@zeniv.linux.org.uk>, Dominik Brodowski <linux@dominikbrodowski.net>, Thomas Gleixner <tglx@linutronix.de>, Andrew Morton <akpm@linux-foundation.org>, linux-alpha@vger.kernel.org, Deepa Dinamani <deepa.kernel@gmail.com> Subject: Re: [PATCH v2 2/2] rusage: allow 64-bit times ru_utime/ru_stime Date: Thu, 21 Jun 2018 18:11:21 +0200 [thread overview] Message-ID: <20180621161121.GB7222@gmail.com> (raw) In-Reply-To: <CAK8P3a1QYTfRNQt2+a29BpvgYM_pnSFrO=NBvVo=BdUa2q9ngQ@mail.gmail.com> * Arnd Bergmann <arnd@arndb.de> wrote: > Sure, no problem. Do you have an opinion on the question I raised in the > first patch [1], i.e. whether we actually want this to be done this way in the > kernel, or one of the other approaches I described there? So this looks like the most forward looking variant: > a) deprecate the wait4() and getrusage() system calls, and create > a set of kernel interfaces based around a newly defined structure that > could solve multiple problems at once, e.g. provide more fine-grained > timestamps. The C library could then implement the posix interfaces > on top of the new system calls. ... but given the pretty long propagation time of new ABIs, is this a good solution? What would the limitations/trade-offs be on old-ABI systems? Thanks, Ingo
next prev parent reply other threads:[~2018-06-21 16:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-20 12:05 [PATCH v2 1/2] y2038: rusage: Use __kernel_old_timeval for process times Arnd Bergmann 2018-04-20 12:05 ` [PATCH v2 2/2] rusage: allow 64-bit times ru_utime/ru_stime Arnd Bergmann 2018-06-21 15:49 ` Ingo Molnar 2018-06-21 16:01 ` Arnd Bergmann 2018-06-21 16:11 ` Ingo Molnar [this message] 2018-06-21 16:25 ` Arnd Bergmann 2018-06-22 2:16 ` Ingo Molnar 2018-06-22 17:45 ` Eric W. Biederman 2018-06-24 7:12 ` Ingo Molnar 2018-06-25 1:26 ` Eric W. Biederman 2018-06-25 9:14 ` Ingo Molnar 2018-06-25 16:21 ` Eric W. Biederman 2018-06-25 11:42 ` Arnd Bergmann
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=20180621161121.GB7222@gmail.com \ --to=mingo@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=arnd@arndb.de \ --cc=deepa.kernel@gmail.com \ --cc=ebiederm@xmission.com \ --cc=eggert@cs.ucla.edu \ --cc=ink@jurassic.park.msu.ru \ --cc=linux-alpha@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@dominikbrodowski.net \ --cc=mattst88@gmail.com \ --cc=rth@twiddle.net \ --cc=tglx@linutronix.de \ --cc=viro@zeniv.linux.org.uk \ --cc=x86@kernel.org \ --cc=y2038@lists.linaro.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: linkBe 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).