On Wed, 2010-11-17 at 12:42 -0800, Davide Libenzi wrote:
quoted text
> On Wed, 17 Nov 2010, Alexander Shishkin wrote:
> 
> > > But what you folks really want for this stuff is an extension to
> > > timerfd as you want to be able to poll, right?
> > > 
> > > So what about the following:
> > > 
> > > Add a new flag TDF_NOTIFY_CLOCK_WAS_SET to the timerfd flags. Now this
> > > flag adds the timer to a separate list, which gets woken up when the
> > > clock is set.
> > > 
> > > No new syscall, just a few lines of code in fs/timerfd.c and
> > > clock_was_set().
> > > 
> > > Thoughts ?
> > 
> > Something like this (sans ugliness)?
> 
> Oh, gosh, please.  This is interface-multiplexing-a-palooza.
> It should be decided if the feature makes sense, and then have proper 
> interface, instead of multiplexing unrelated insterfaces.
> This is a sort of system-event-report pattern.  What is wrong with using a 
> netlink-based transport for those kind of things?

Could you please explain in more details what is the problem?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/