[lkml]   [2010]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[RFC PATCH] poll(): add poll_wait_set_exclusive()
    Executive summary:

    Addition of the new internal API:

    poll_wait_set_exclusive() : set poll wait queue to exclusive

    Sets up a poll wait queue to use exclusive wakeups. This is useful to
    wake up only one waiter at each wakeup. Used to work-around "thundering herd"

    * Problem description :

    In the ring buffer poll() implementation, a typical multithreaded user-space
    buffer reader polls all per-cpu buffer descriptors for data. The number of
    reader threads can be user-defined; the motivation for permitting this is that
    there are typical workloads where a single CPU is producing most of the tracing
    data and all other CPUs are idle, available to consume data. It therefore makes
    sense not to tie those threads to specific buffers. However, when the number of
    threads grows, we face a "thundering herd" problem where many threads can be
    woken up and put back to sleep, leaving only a single thread doing useful work.

    * Solution :

    Introduce a poll_wait_set_exclusive() primitive to poll API, so the code which
    implements the pollfd operation can specify that only a single waiter must be
    woken up.

    To Andi's question:

    > How does that work?

    I let the ring buffer poll file operation calls a new:


    Which makes sure that when we have multiple threads waiting on the same file
    descriptor (which represents a ring buffer), only one of the threads is woken

    > Wouldn't that break poll semantics?

    The way I currently do it, yes, but we might be able to do better by tweaking
    the poll wakeup chain.

    Basically, what I need is that a poll wakeup triggers an exclusive synchronous
    wakeup, and then re-checks the wakeup condition. AFAIU, the usual poll semantics
    seems to be that all poll()/epoll() should be notified of state changes on all
    examined file descriptors. But wether we should do the wakeup first, wait for
    the woken up thread to run (possibly consume the data), and then only after that
    check if we must continue going through the wakeup chain is left as a grey zone

    > If not it sounds like a general improvement.
    > I assume epoll already does it?

    Nope, if I believe epoll(7):

    " Q2 Can two epoll instances wait for the same file descriptor? If so,
    are events reported to both epoll file descriptors?

    A2 Yes, and events would be reported to both. However, careful pro‐

    So for now, I still propose the less globally intrusive approach, with
    poll_wait_set_exclusive(). Maybe if we figure out that changing the poll wakeup
    chains behavior is appropriate, we can proceed differently.

    This patch is based on top of:

    branch: tip-pull-queue

    Signed-off-by: Mathieu Desnoyers <>
    CC: William Lee Irwin III <>
    CC: Ingo Molnar <>
    CC: Andi Kleen <>
    CC: Steven Rostedt <>
    CC: Peter Zijlstra <>
    fs/select.c | 41 ++++++++++++++++++++++++++++++++++++++---
    include/linux/poll.h | 2 ++
    2 files changed, 40 insertions(+), 3 deletions(-)

    Index: linux.trees.git/fs/select.c
    --- linux.trees.git.orig/fs/select.c 2010-07-09 15:59:00.000000000 -0400
    +++ linux.trees.git/fs/select.c 2010-07-09 16:03:24.000000000 -0400
    @@ -112,6 +112,9 @@ struct poll_table_page {
    static void __pollwait(struct file *filp, wait_queue_head_t *wait_address,
    poll_table *p);
    +static void __pollwait_exclusive(struct file *filp,
    + wait_queue_head_t *wait_address,
    + poll_table *p);

    void poll_initwait(struct poll_wqueues *pwq)
    @@ -152,6 +155,20 @@ void poll_freewait(struct poll_wqueues *

    + * poll_wait_set_exclusive - set poll wait queue to exclusive
    + *
    + * Sets up a poll wait queue to use exclusive wakeups. This is useful to
    + * wake up only one waiter at each wakeup. Used to work-around "thundering herd"
    + * problem.
    + */
    +void poll_wait_set_exclusive(poll_table *p)
    + if (p)
    + init_poll_funcptr(p, __pollwait_exclusive);
    static struct poll_table_entry *poll_get_entry(struct poll_wqueues *p)
    struct poll_table_page *table = p->table;
    @@ -213,8 +230,10 @@ static int pollwake(wait_queue_t *wait,

    /* Add a new entry */
    -static void __pollwait(struct file *filp, wait_queue_head_t *wait_address,
    - poll_table *p)
    +static void __pollwait_common(struct file *filp,
    + wait_queue_head_t *wait_address,
    + poll_table *p,
    + int exclusive)
    struct poll_wqueues *pwq = container_of(p, struct poll_wqueues, pt);
    struct poll_table_entry *entry = poll_get_entry(pwq);
    @@ -226,7 +245,23 @@ static void __pollwait(struct file *filp
    entry->key = p->key;
    init_waitqueue_func_entry(&entry->wait, pollwake);
    entry->wait.private = pwq;
    - add_wait_queue(wait_address, &entry->wait);
    + if (!exclusive)
    + add_wait_queue(wait_address, &entry->wait);
    + else
    + add_wait_queue_exclusive(wait_address, &entry->wait);
    +static void __pollwait(struct file *filp, wait_queue_head_t *wait_address,
    + poll_table *p)
    + __pollwait_common(filp, wait_address, p, 0);
    +static void __pollwait_exclusive(struct file *filp,
    + wait_queue_head_t *wait_address,
    + poll_table *p)
    + __pollwait_common(filp, wait_address, p, 1);

    int poll_schedule_timeout(struct poll_wqueues *pwq, int state,
    Index: linux.trees.git/include/linux/poll.h
    --- linux.trees.git.orig/include/linux/poll.h 2010-07-09 15:59:00.000000000 -0400
    +++ linux.trees.git/include/linux/poll.h 2010-07-09 16:03:24.000000000 -0400
    @@ -79,6 +79,8 @@ static inline int poll_schedule(struct p
    return poll_schedule_timeout(pwq, state, NULL, 0);

    +extern void poll_wait_set_exclusive(poll_table *p);
    * Scaleable version of the fd_set.
    Mathieu Desnoyers
    Operating System Efficiency R&D Consultant
    EfficiOS Inc.
    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: 2010-10-06 19:59    [W:0.032 / U:223.384 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site