search for: mm_get_bio_cgroup

...of pid, or tid, to cgroups? -- what ID is OK to write to "tasks" file and what we can expect as a result? Tsuruta-san, how about your bio-cgroup's tracking concerning this? If we want to use your tracking functions for each threads seperately, there seems to be a problem. ===cf. mm_get_bio_cgroup()=================== owner mm_struct ----> task_struct ----> bio_cgroup ============================================= In my understanding, the mm_struct of a thread is same as its parent's. So, even if we attach the TIDs of some threads to different cgroups the tracking always...

...of pid, or tid, to cgroups? -- what ID is OK to write to "tasks" file and what we can expect as a result? Tsuruta-san, how about your bio-cgroup's tracking concerning this? If we want to use your tracking functions for each threads seperately, there seems to be a problem. ===cf. mm_get_bio_cgroup()=================== owner mm_struct ----> task_struct ----> bio_cgroup ============================================= In my understanding, the mm_struct of a thread is same as its parent's. So, even if we attach the TIDs of some threads to different cgroups the tracking always...

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team