From: Alexander Shishkin <virtuoso@slind.org>
To: Greg KH <gregkh@suse.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
john stultz <johnstul@us.ibm.com>,
lkml@vger.kernel.org, "Kirill A. Shutemov" <kirill@shutemov.name>,
Thomas Gleixner <tglx@linutronix.de>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jon Hunter <jon-hunter@ti.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>, Avi Kivity <avi@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, John Kacur <jkacur@redhat.com>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <virtuoso@slind.org>
Subject: Re: [PATCH] [RFC] notify userspace about time changes
Date: Fri, 6 Aug 2010 10:21:45 +0300 [thread overview]
Message-ID: <20100806072145.GG28519@shisha.kicks-ass.net> (raw)
In-Reply-To: <20100805223854.GA19511@suse.de>
On Thu, Aug 05, 2010 at 03:38:54 -0700, Greg KH wrote:
> On Fri, Aug 06, 2010 at 12:22:27AM +0200, Kay Sievers wrote:
> > On Thu, Aug 5, 2010 at 23:38, Greg KH <gregkh@suse.de> wrote:
> > > On Thu, Aug 05, 2010 at 02:11:05PM -0700, john stultz wrote:
> > >> On Thu, 2010-08-05 at 15:33 +0300, Alexander Shishkin wrote:
> > >> > On 4 August 2010 18:58, john stultz <johnstul@us.ibm.com> wrote:
> > >> > > Is there a actual use case that you need this for? I don't really have
> > >> > > an issue with the code I just really want to make sure the feature would
> > >> > > be useful enough to justify the API and code maintenance going forward.
> > >> >
> > >> > Yes. What we have here is an application which takes care of different means
> > >> > of time synchronization (trusted time servers, different GSM operators, etc)
> > >> > and also different kinds of time-based events/notifications (like "dentist
> > >> > appointment next thursday"). When it encounters a time change that is
> > >> > made by some other application, it basically wants to disable automatic
> > >> > time adjustment and trigger the events/notifications which are due at this
> > >> > (new) time.
> > >>
> > >> Ok. Something specific is always more helpful then theoretical uses.
> > >>
> > >> I think the filtering is still a bit controversial, so you might want to
> > >> respin it without that. But otherwise I'm ok with it as long as no one
> > >> else objects to any of the minor details of the interface
> > >>
> > >> GregKH: Does /sys/kernel/time_notify seem ok by you?
> > >
> > > Um, it depends, what is that file going to do? I don't see a
> > > Documentation/ABI/ entry here that describes it fully :)
> >
> > I think that's really awkward interface, to pass file descriptor
> > numbers around and write them to magic sysfs files.
>
> Ick, really? That's not ok for sysfs.
This is how cgroups notifications work [1], for example. One obtains an
eventfd, one then writes its descriptor to a certain control file, one polls
said eventfd for events. The type of event is echoed to the same control file
together with the fd.
So, my idea was, basically to use the sysfs file as means to specify what
kind of time-related events a program wants to subscribe to. For example,
<int:eventfd descriptor> <bool:want other's time changes> <bool:want own time
changes> <bool:want settimeofday> <bool:want adjtime>
> > I would very much prefer a file that contains the current time, and
> > wakes up possible users with a POLL_ERR on changes caused by some
> > other process. That works very well for things like /proc/mounts, is
> > easy to get, and does not need a full page of weird instructions to
> > get stuff done. :)
>
> That sounds more reasonable.
Polling a simple sysfs file is not enough as I described in the other mail,
unless it implements a counter similar to eventfd, which would effectively
make it another eventfd implementation, only with a dentry this time.
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=kernel/cgroup.c;h=a8ce099544049e787464c3e4261ac70625cc0653;hb=HEAD#l3071 onwards
Regards,
--
Alex
next prev parent reply other threads:[~2010-08-06 7:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 12:48 Alexander Shishkin
2010-08-04 12:54 ` Bastien ROUCARIES
2010-08-04 15:49 ` Alexander Shishkin
2010-08-04 15:32 ` Kirill A. Shutemov
2010-08-04 15:46 ` Alexander Shishkin
2010-08-05 10:05 ` Kirill A. Shutemov
2010-08-04 15:58 ` john stultz
2010-08-04 18:48 ` Chris Friesen
2010-08-05 0:52 ` john stultz
2010-08-05 12:39 ` Alexander Shishkin
2010-08-05 14:10 ` Chris Friesen
2010-08-05 12:33 ` Alexander Shishkin
2010-08-05 21:11 ` john stultz
2010-08-05 21:38 ` Greg KH
2010-08-05 22:22 ` Kay Sievers
2010-08-05 22:34 ` H. Peter Anvin
2010-08-05 22:39 ` Kay Sievers
2010-08-05 22:43 ` H. Peter Anvin
2010-08-05 22:38 ` Greg KH
2010-08-06 7:21 ` Alexander Shishkin [this message]
2010-08-06 23:44 ` Greg KH
2010-08-06 7:11 ` Alexander Shishkin
2010-08-06 7:43 ` Bastien ROUCARIES
2010-08-05 22:17 ` Kay Sievers
2010-08-05 22:29 ` john stultz
2010-08-05 22:30 ` john stultz
2010-08-05 23:50 ` Kay Sievers
2010-08-06 0:16 ` john stultz
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=20100806072145.GG28519@shisha.kicks-ass.net \
--to=virtuoso@slind.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=dhowells@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=jkacur@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=jon-hunter@ti.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--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®