[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070331130149.GA18345@infradead.org>
Date: Sat, 31 Mar 2007 14:01:49 +0100
From: Christoph Hellwig <hch@...radead.org>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: "Stone, Joshua I" <joshua.i.stone@...el.com>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
SystemTAP <systemtap@...rces.redhat.com>,
Satoshi Oshima <soshima@...hat.com>,
Hideo Aoki <haoki@...hat.com>,
Yumiko Sugita <yumiko.sugita.yf@...achi.com>, hch@...radead.org
Subject: Re: [RFC][Patch 1/4] kprobe fast unregistration
On Fri, Mar 23, 2007 at 02:22:48PM -0400, Frank Ch. Eigler wrote:
> Really? What possible problems can occur? The worst that occurs to
> me is that if someone forgets to call the commit function, the kprobes
> will still be disabled, but memory won't be recycled for a while.
Exactly. It's a very unintuitive interface, exposing implementation
details to the user. The array variant otoh is obvious to the user:
gice me an array of probes to register/unregister and do it.
> Would it be possible to allay even that concern with an automated
> deferred/periodic commit?
That's even worse from the user perspective interface.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists