linux-kernel - Re: [PATCH 1/3] accounting: task counters for disk/network

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 10 Apr 2008 12:41:58 +0900 (JST)
From:	Hirokazu Takahashi <taka@...inux.co.jp>
To:	gerlof@...omputing.nl
Cc:	menage@...gle.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, balbir@...ibm.com, xemul@...nvz.org
Subject: Re: [PATCH 1/3] accounting: task counters for disk/network

Hi Gerlof,

> >  This sort of accounting will presumably be needed by a disk bandwidth
> >  cgroup controller.  Perhaps the containers/cgroup people have plans of code
> >  already?
> >
> 
> Yes, there have been various cgroup block-I/O subsystems proposed. I
> know that at least the one posted by Hirokazu Takahashi
> <taka@...inux.co.jp> uses the same per-page cgroup pointer as the
> memory controller.

Yes, I'm working on this.

linux-2.6.25-rc series now have the memory controller in them, which
supports to get the cgroup from any pageframe. I made a block-I/O
controller on it experimentally.

If you use this controller with dm-ioband, which is an engine implemented
as a device mapper module to control the bandwidth of block I/Os,
you can also get "cgroup block I/O accounting" from it.

I guess you can enhance this controller to track the I/Os per process
if you really want to. But it will cause extra overhead which I think
you may not ignore.

Thanks,
Hirokazu Takahashi.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/