On Wednesday 23 August 2006 13:03, Kirill Korotaev wrote:it was kernel/ub/proc.c with proc interface :)
+#ifdef CONFIG_BEANCOUNTERS
+extern struct hlist_head bc_hash[];
+extern spinlock_t bc_hash_lock;
I wonder who pokes into that hash from other files? Looks a bit dangerous.
yep, almost the same reason :)+void __put_beancounter(struct beancounter *bc);
+static inline void put_beancounter(struct beancounter *bc)
+{
+ __put_beancounter(bc);
+}
The wrapper seems pointless too.
The file could use a overview comment what the various counteryou mean comment about what resource parameters we introduce?
types actually are.
only due to code bugs.+ bc_print_id(bc, uid, sizeof(uid));
+ printk(KERN_WARNING "BC %s %s warning: %s "
Doesn't this need some rate limiting? Or can it be only triggered
by code bugs?
:))+ bc = &default_beancounter;
+ memset(bc, 0, sizeof(default_beancounter));
You don't trust the BSS to be zero? @)