lkml.org 
[lkml]   [2003]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [ANNOUNCE] udev 0.1 release
    On Fri, Apr 11, 2003 at 03:09:33PM -0700, Andrew Morton wrote:
    > Steven Dake <sdake@mvista.com> 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.
    >
    > 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.

    But how many events to we buffer? When do we start to throw them away?
    Fun policy decisions that we don't have to worry about in the current
    scheme.

    Also, what's the format of the kernel->user interface. Today with
    /sbin/hotplug it's a very simple, and easily changed interaction. Using
    a event reading mechanism lends itself to binary interfaces, which have
    to be kept in sync with user code very tightly.

    And yes, we could use ascii in the event list, but then again, a
    userspace version of /sbin/hotplug that writes events to a pipe that is
    read from a daemon enables the same thing to happen :)

    thanks,

    greg k-h
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:34    [W:5.111 / U:0.956 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site