svn commit: r278479 - in head: etc sys/kern

[John-Mark Gurney]

John Baldwin wrote this message on Tue, Feb 10, 2015 at 10:36 -0500:
> > I think devd grows these things because it's easier than teaching the
> > devctl interface to support multiple listeners.
> 
> That wasn't really my question.  My question was if we want distinct streams 
> or if we want want unified stream.  Having a unified stream might very well 
> make sense (and if so we could rename devd to make that more obvious).

The biggested issue that I see w/ using devd as the gateway is that
as we add more events, devd will now have to be woken up for ALL events,
even when the even has no listeners for it...  If we keep adding events,
this will be very bad for laptop battery life...

This is becoming a standard pub/sub type problem, and there is plenty
of research/programs out there that already does this...

As someone mentioned earlier, it seems like using kqueue is starting
to make more sense for this type of thing where various programs can
select what they get woken up for...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."