I'm looking for feedback on this patch.... and (feedback) on future IPv6 MIB stats patches if anyone cares to go that far. This patch modifies the ICMPv6 MIB statistics to be collected per network-i
We, USAGI, have similar code for linux-2.4. (Sorry, I forgot this one... :-p) We store per-interface in inet6_dev{}, because this information blongs to inet6 layer. I'd recommend that we split inform
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> Date: Tue, 15 Apr 2003 00:29:15 +0900 (JST) I'd recommend that we split information per interface 1) to minimize the /proc file 2) to minimize
Hi, I'm looking for feedback on this patch.... and (feedback) on future IPv6 MIB stats patches if anyone cares to go that far. This patch modifies the ICMPv6 MIB statistics to be collected per networ
We, USAGI, have similar code for linux-2.4. (Sorry, I forgot this one... :-p) We store per-interface in inet6_dev{}, because this information blongs to inet6 layer. I'd recommend that we split inform
From: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx> Date: Tue, 15 Apr 2003 00:29:15 +0900 (JST) I'd recommend that we split information per interface 1) to minimize the /proc file 2) to minimize the
Yes, sounds good. Is this something that you plan to extract from the USAGI Linux 2.4 patches and submit for 2.5, or should I continue with my patches? Thanks, -- ~Randy
Please let me see your patch in details. I'll do it today... (It is 2:00am... I'm sleepy... zzz...) -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D
BTW, for example, if we do if_indextoname() will return foobar. we, however, will see /proc/sys/net/ipv6/conf/eth9 instead of /proc/sys/net/ipv6/conf/foobar. This is not good. Is this just a bug not