[lkml]   [2003]   [Apr]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [ANNOUNCE] udev 0.1 release
    Andrew Morton wrote:
    > Steven Dake <> wrote:
    >>A much better solution could be had by select()ing on a filehandle
    >>indicating when a new hotswap event is ready to be processed. No races,
    >>no security issues, no performance issues.
    > I must say that I've always felt this to be a better approach than the
    > /sbin/hotplug callout.

    Better in some environments, not all. It's a tradeoff.

    Me, I'd far rather allocate those hotplug resources on demand
    than pre-allocate them into Yet Another Daemon. For bounded
    response-time systems, or for systems that are generating huge
    event streams, I'd likely want more control though.

    > Apart from the performance issue, it means that the kernel can buffer the
    > "insertion" events which happen at boot-time discovery until the userspace
    > handler attaches itself.

    It could do that regardless of whether the event is eventually
    delivered through some socket or by spawning a new process.

    The way hotplug events are handled after some subsystem decides
    to send them isn't written in stone. They've been asynchronous
    all through the 2.4 series, so queueing is semantically OK.

    - Dave

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:34    [W:3.363 / U:0.056 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site