> The reason is that the work is generated so often that a work is not > finished before next work of same type comes. This is especially true > for transmit and receive. Then I get 0 back when queuing the work and > there is no real way to solve it from what I can see than to allocate > new work structures every time. So if that is the case what bounds your memory usage - can a busy box end up with thousands of work queue slos used ? It sounds like your model is perhaps wrong - if there is a continual stream of work maybe you should simply have a kernel thread to handle it if it cannot be deferred - remember ldisc code is able to sleep in most paths. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
