Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\]\s+watch64\:\s+generic\s+variable\s+monitoring\s+system\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\]\s+watch64\:\s+generic\s+variable\s+monitoring\s+system\s*$/: 18 ]

Total 18 documents matching your query.

1. [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: ezwanul_Kabir@xxxxxxxx>; Date: Fri, 03 Sep 2004 13:19:24 -0400; The watch64 system allows the programmer to specify the approximate interval at which he wants his variables checked. If he tries to specify shorter interval than the minimum a default value of HZ/10; /archives/netdev/2004-09/msg00088.html (21,709 bytes)
2. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: atiev <vkondra@xxxxxxx>; Date: Sat, 04 Sep 2004 04:07:27 +0900 (JST); I agree with the basic principle; it is very similar to mine. However, it is too complicated isn't it? I would do per-"table" registration (instead of per-variable one); watch64_getval() seems very u; /archives/netdev/2004-09/msg00092.html (10,295 bytes)
3. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: ‹±وکژ <yoshfuji@xxxxxxxxxxxxxx>; Date: Fri, 03 Sep 2004 16:24:15 -0400; Yes, I saw a patch on lkml a while a go (possibly yours?) that used a workqueue (IIRC.) I considered the option of removing the capability of the programmer asking for a certain interval, and instead; /archives/netdev/2004-09/msg00093.html (10,699 bytes)
4. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Fri, 03 Sep 2004 16:40:30 -0400; The following fixes watch64 patch previously submitted to follow CodingStyle guidelines. BK repo is up to date as well Jeff. Signed-off-by: Josef "Jeff" Sipek <jeffpc@xxxxxxxxxxxxx> -- 1.7/kernel/wat; /archives/netdev/2004-09/msg00095.html (11,649 bytes)
5. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: >; Date: Fri, 03 Sep 2004 17:44:24 -0400; Sorry about the white space, KMail apparently likes to butcher the text. These are the same patches with the little cleanup update. Jeff. - -- Reality is merely an illusion, albeit a very persistent; /archives/netdev/2004-09/msg00097.html (10,435 bytes)
6. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: 04 Sep 2004 09:19:59 -0400; I have a feeling this was discussed somewhere(other than netdev) and i missed it. Why isnt this watch64 being done in user space? cheers, jamal; /archives/netdev/2004-09/msg00101.html (10,721 bytes)
7. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: rzysztof Halasa <khc@xxxxxxxxx>; Date: Sun, 05 Sep 2004 12:19:34 -0400; There was a discussion about 64-bit network statistics about a year ago on lkml. watch64 is a generic so that anyone in the kernel can use it. Jeff. - -- Mankind invented the atomic bomb, but no mous; /archives/netdev/2004-09/msg00130.html (10,102 bytes)
8. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: xxxx>; Date: 07 Sep 2004 06:18:11 -0400; Sorry unsubscribed from lkml since summer of '94. [net related discussions should really happen on netdev]. Ok - so why does this have to be in the kernel? cheers, jamal; /archives/netdev/2004-09/msg00154.html (10,330 bytes)
9. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: >; Date: Sun, 12 Sep 2004 11:53:44 -0400; es have; /archives/netdev/2004-09/msg00365.html (10,446 bytes)
10. [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: "Josef 'Jeff' Sipek" <jeffpc@xxxxxxxxxxxxx>; Date: Fri, 03 Sep 2004 13:19:24 -0400; The watch64 system allows the programmer to specify the approximate interval at which he wants his variables checked. If he tries to specify shorter interval than the minimum a default value of HZ/10; /archives/netdev/2004-09/msg01544.html (21,790 bytes)
11. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: YOSHIFUJI Hideaki / <yoshfuji@xxxxxxxxxxxxxx>; Date: Sat, 04 Sep 2004 04:07:27 +0900 (JST); I agree with the basic principle; it is very similar to mine. However, it is too complicated isn't it? I would do per-"table" registration (instead of per-variable one); watch64_getval() seems very u; /archives/netdev/2004-09/msg01548.html (10,394 bytes)
12. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: Jeff Sipek <jeffpc@xxxxxxxxxxxxx>; Date: Fri, 03 Sep 2004 16:24:15 -0400; Yes, I saw a patch on lkml a while a go (possibly yours?) that used a workqueue (IIRC.) I considered the option of removing the capability of the programmer asking for a certain interval, and instead; /archives/netdev/2004-09/msg01549.html (10,863 bytes)
13. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: "Josef 'Jeff' Sipek" <jeffpc@xxxxxxxxxxxxx>; Date: Fri, 03 Sep 2004 16:40:30 -0400; The following fixes watch64 patch previously submitted to follow CodingStyle guidelines. BK repo is up to date as well Jeff. Signed-off-by: Josef "Jeff" Sipek <jeffpc@xxxxxxxxxxxxx> -- 1.7/kernel/wat; /archives/netdev/2004-09/msg01551.html (11,863 bytes)
14. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: "Josef 'Jeff' Sipek" <jeffpc@xxxxxxxxxxxxx>; Date: Fri, 03 Sep 2004 17:44:24 -0400; Sorry about the white space, KMail apparently likes to butcher the text. These are the same patches with the little cleanup update. Jeff. - -- Reality is merely an illusion, albeit a very persistent; /archives/netdev/2004-09/msg01553.html (10,619 bytes)
15. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 04 Sep 2004 09:19:59 -0400; I have a feeling this was discussed somewhere(other than netdev) and i missed it. Why isnt this watch64 being done in user space? cheers, jamal; /archives/netdev/2004-09/msg01557.html (10,912 bytes)
16. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: Jeff Sipek <jeffpc@xxxxxxxxxxxxx>; Date: Sun, 05 Sep 2004 12:19:34 -0400; There was a discussion about 64-bit network statistics about a year ago on lkml. watch64 is a generic so that anyone in the kernel can use it. Jeff. - -- Mankind invented the atomic bomb, but no mous; /archives/netdev/2004-09/msg01586.html (10,234 bytes)
17. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 07 Sep 2004 06:18:11 -0400; Sorry unsubscribed from lkml since summer of '94. [net related discussions should really happen on netdev]. Ok - so why does this have to be in the kernel? cheers, jamal; /archives/netdev/2004-09/msg01610.html (10,495 bytes)
18. Re: [PATCH 2.6] watch64: generic variable monitoring system (score: 1): Author: Jeff Sipek <jeffpc@xxxxxxxxxxxxx>; Date: Sun, 12 Sep 2004 11:53:44 -0400; Sorry, I missed your email. netdev was CC'd during this whole discussion. I think it is convenient to have the 64 bit net stats reported by the kernel. Jeff. - -- My public GPG key can be found at ht; /archives/netdev/2004-09/msg01821.html (10,591 bytes)

Current List: 1 - 18
Page: [1]