| To: | Jeff Sipek <jeffpc@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6] watch64: generic variable monitoring system |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 07 Sep 2004 06:18:11 -0400 |
| Cc: | Stephen Hemminger <shemminger@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200409051219.47590.jeffpc@xxxxxxxxxxxxx> |
| Organization: | jamalopolis |
| References: | <200409031307.01240.jeffpc@xxxxxxxxxxxxx> <200409031744.32970.jeffpc@xxxxxxxxxxxxx> <1094303999.1633.116.camel@xxxxxxxxxxxxxxxx> <200409051219.47590.jeffpc@xxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Sun, 2004-09-05 at 12:19, Jeff Sipek wrote: > On Saturday 04 September 2004 09:19, jamal wrote: > > I have a feeling this was discussed somewhere(other than netdev) and i > > missed it. Why isnt this watch64 being done in user space? > > There was a discussion about 64-bit network statistics about a year ago on > lkml. Sorry unsubscribed from lkml since summer of '94. [net related discussions should really happen on netdev]. > watch64 is a generic so that anyone in the kernel can use it. Ok - so why does this have to be in the kernel? cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] mark mace and bmac as ppc32 only, Olaf Hering |
|---|---|
| Next by Date: | [PATCH] Trivial fix for out of bounds array access in xfrm4_policy_check, Catalin(ux aka Dino) BOIE |
| Previous by Thread: | Re: [PATCH 2.6] watch64: generic variable monitoring system, Jeff Sipek |
| Next by Thread: | Re: [PATCH 2.6] watch64: generic variable monitoring system, Jeff Sipek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |