lkml.org 
[lkml]   [2012]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] epoll: Improved support for multi-threaded clients
    Christof,

    We believe that EPOLLONESHOT is required in order to make any
    sensible use of calling epoll_wait on a single epoll set concurrently
    in multiple threads. So in that sense the new functionality is really
    only useful for coordinating resource deletion between threads when
    using EPOLLONESHOT. However, when EPOLLONESHOT is not used,
    EPOLL_CTL_DISABLE still disables the item, and can be used solely for
    that purpose if the caller intends to re-enable the item via
    EPOLL_CTL_MOD and doesn't wish to incur the additional overhead
    associated with deleting and re-adding an item.

    Thank you,
    Pat

    At 6/16/2012 11:47 AM, Christof Meerwald wrote:
    >On Mon, 11 Jun 2012 15:34:49 -0700, Paton Lewis wrote:
    > > This patch introduces the new epoll_ctl command EPOLL_CTL_DISABLE, which
    > > disables the associated epoll item and returns -EBUSY if the
    > epoll item is not
    > > currently in the epoll ready queue. This allows multiple threads to use a
    > > mutex to determine when it is safe to delete an epoll item and
    > its associated
    > > resources. This allows epoll items to be deleted and closed efficiently and
    > > without error.
    >
    >Do you assume that EPOLLONESHOT is being used for this to work or
    >would you expect your patch to also address the case where
    >EPOLLONESHOT is not used?
    >
    >
    >Christof
    >
    >--
    >
    >http://cmeerw.org sip:cmeerw at cmeerw.org
    >mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org



    \
     
     \ /
      Last update: 2012-06-19 02:01    [W:0.024 / U:29.288 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site