Hi Kamezawa-san, KAMEZAWA Hiroyuki wrote: > On Wed, 20 Aug 2008 16:12:47 +0900 (JST) > Hirokazu Takahashi <taka@xxxxxxxxxxxxx> wrote: > >> - I think this kind of thread application should control its I/O requests >> inside of the application. I guess it seems to quite difficult to >> determine which thread is doing what kind of job in the application. >> We can just leave this issue to these type of applications, can we? >> I guess most of this kind of applications must have been well designed >> already. >> > I agree. (it's better to postpone this.) > > But maybe cpuset (HPC) applications uses per-thread cgroup attachment. > So, I can't say there is no trouble even if we ignore threads. > Thank you for details. I feel that we are near a consensus on this problem. To make clear this not only for developers but also for users what do you think about making documentation and implementing can_attach() to avoid not presumed attachments? For example, 1. reject attachments of threads by can_attach(), 2. explain about what will and will not happen if we attach threads, ... Thanks, Yoshikawa _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
