>>>>> "John" == John Hesterberg <[EMAIL PROTECTED]> writes:
John> I believe the accounting our customers require needs to be John> turned on system-wide. In fact, I recall getting problems John> reports if there are some processes not 'accounted' for. If you John> do it on a task basis, and accounting gets turned on, you'd have John> to have a fool-proof way of tracking down all the tasks in a John> system and turn on their accounting. Thats what I was scared someone would say ;-( The problem I am seeing is that SGI wants certain things in the accounting block, I am sure IBM has other things they wish to count and someone else will want to count something else again. With all those numbers we may end up with a relatively large block for accounting numbers in struct task_struct. However it makes it a lot harder to use the task_notifiers for it ;-( John> I would expect sites either want accounting on all the time for John> everything, or not at all. Right now a lot of the accounting is done by calling into a function which checks a flag for whether accounting is enabled and returns if it is not. That could easily be extended to check for the global accounting flag + check that the task's accounting data structure has been allocated. Then in certain places, like fork() and schedule(), allocate it if it's not in place already and accounting has been switched on. That way we could reduce the overhead to a single pointer in struct task_struct and the accounting structure could (in theory) grow indefinately large. Or is this too much of a hack? Comments? Cheers, Jes ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
