On Wednesday, October 22, 2014 8:49 AM, Nicolas Pitre [n...@fluxnic.net] wrote:
On Wed, 22 Oct 2014, Rob Landley wrote:
On 10/21/14 14:58, Nicolas Pitre wrote:
On Tue, 21 Oct 2014, Bird, Tim wrote:
I'm going to respond to several comments in this one message (sorry for
the likely
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not sure why this attention to reading the status. The salient feature
here is that the initializations are deferred until user space tells the
kernel
to proceed. It's the initiation of the trigger from user-space that matters.
The whole purpose
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not sure why this attention to reading the status. The salient feature
here is that the initializations are deferred until user space tells the
kernel
to proceed. It's the initiation of
On 10/23/14 12:21, Bird, Tim wrote:
On Wednesday, October 22, 2014 8:49 AM, Nicolas Pitre [n...@fluxnic.net]
wrote:
On Wed, 22 Oct 2014, Rob Landley wrote:
Otherwise the standard hotplug notification mechanism is already
available.
I'm not sure why this attention to reading the status.
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not sure why this attention to reading the status. The salient
feature
here is that the initializations are deferred until user space
On Thursday, October 23, 2014 12:05 PM, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not sure why this attention to reading the status. The salient
feature
On Thu, 23 Oct 2014, Bird, Tim wrote:
On Thursday, October 23, 2014 12:05 PM, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not sure why this attention to
On 10/23/14 14:05, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
Why a trigger? I'm suggesting no trigger at all is needed.
Let all initcalls start initializing whenever they
On 10/23/14 15:50, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Bird, Tim wrote:
On Thursday, October 23, 2014 12:05 PM, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
I'm not
On Thu, 23 Oct 2014, Rob Landley wrote:
On 10/23/14 14:05, Nicolas Pitre wrote:
On Thu, 23 Oct 2014, Alexandre Belloni wrote:
On 23/10/2014 at 13:56:44 -0400, Nicolas Pitre wrote :
On Thu, 23 Oct 2014, Bird, Tim wrote:
Why a trigger? I'm suggesting no trigger at all is needed.
On Thu, 23 Oct 2014, Rob Landley wrote:
Doing hardware probing at low priorities can cause really _fun_ latency
spikes in the system as something grabs a lock and then sleeps. (And
doing this at the realtime scheduling where it won't do that translates
those latency spikes into the
11 matches
Mail list logo
