From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6] watch64: generic variable monitoring system
Date: Fri, 3 Sep 2004 12:16:57 -0700 [thread overview]
Message-ID: <20040903121657.355a6a8b@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <200409031319.24863.jeffpc@optonline.net>
On Fri, 03 Sep 2004 13:19:24 -0400
"Josef 'Jeff' Sipek" <jeffpc@optonline.net> wrote:
> 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 is used. To minimize
> locking, RCU and seqlock are used. On 64-bit systems, all is optimized away.
>
> The following patch can be also pulled from http://jeffpc.bkbits.net/watch64-2.6
>
> Josef "Jeff" Sipek.
>
> Signed-off-by: Josef "Jeff" Sipek <jeffpc@optonline.net>
- Seems like a big interface for a simple problem.
- Code doesn't match the kernel style (read Documentation/CodingStyle)
- Does it really need RCU and seqlock, wouldn't one suffice
next prev parent reply other threads:[~2004-09-03 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 17:06 [PATCH/RFC 2.6] NET: 64-bit network statistics josef Jeff Sipek
2004-09-03 17:19 ` [PATCH 2.6] watch64: generic variable monitoring system Josef 'Jeff' Sipek
2004-09-03 19:07 ` YOSHIFUJI Hideaki / 吉藤英明
2004-09-03 19:16 ` Stephen Hemminger [this message]
2004-09-03 20:18 ` Jeff Sipek
2004-09-03 20:40 ` Josef 'Jeff' Sipek
2004-09-03 21:44 ` Josef 'Jeff' Sipek
2004-09-04 13:19 ` jamal
2004-09-05 16:19 ` Jeff Sipek
2004-09-07 10:18 ` jamal
2004-09-12 15:53 ` Jeff Sipek
2004-09-03 17:22 ` [PATCH 2.6] 64network: 64-bit network statistics Josef 'Jeff' Sipek
2004-09-03 17:24 ` [PATCH/RFC 2.6] NET: " Jeff Sipek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040903121657.355a6a8b@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®