[lkml]   [1998]   [Jun]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Thread implementations...
    Hello, world!\n

    > This demonstrates the point that select and poll are workarounds for
    > the lack of threading support in Unix. They aren't needed if you use
    > a threads facility (or a separate process for each thread you need).
    > Once you have threads you can stick to the intuitive synchronous model
    > of system calls, which has always effectively handled waking one of
    > multiple waiters.

    Not as effectively as it would seem at the first sight. If you decide
    to use multithreading, you eat lots of memory and (which is probably more
    important) lots of L2 cache for thread stacks.

    A possible solution could be extending of the SIGIO concept in the
    following way:

    - SIGIO handler gets an extra parameter containing the FD
    in being reported.

    - FASYNC gets split to read and write part

    Have a nice fortnight
    Martin `MJ' Mares <>
    Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
    "Uncle Ed's Rule of Thumb: Never use your thumb for a rule."

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to

     \ /
      Last update: 2005-03-22 13:43    [W:0.020 / U:0.764 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site