Possibly stupid question: Is it true that any given task can only be using one wait_queue_t at a time? If so, would it be an idea to put a wait_queue_t into struct task_struct [maybe union'ed with a struct wait_bit_queue] and avoid allocating this 40 byte structure repeatedly on the stack.
E.g., in one of Minchan's stack traces, there are two calls of mempool_alloc (which itself declares a wait_queue_t) and one try_to_free_pages (which is the only caller of throttle_direct_reclaim, which in turn uses wait_event_interruptible_timeout and wait_event_killable). Rasmus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
