From: Jes Sorensen <jes@sgi.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@osdl.org>,
Chandra Seetharaman <sekharan@us.ibm.com>,
Keith Owens <kaos@sgi.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/8] Notifier chain update
Date: 19 Jan 2006 05:01:30 -0500 [thread overview]
Message-ID: <yq0mzhs7czp.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060118221525.GI16285@kvack.org>
>>>>> "Benjamin" == Benjamin LaHaise <bcrl@kvack.org> writes:
Benjamin> On Wed, Jan 18, 2006 at 05:09:10PM -0500, Alan Stern wrote:
>> On Wed, 18 Jan 2006, Benjamin LaHaise wrote:
>>
>> > The notifier interface is supposed to be *light weight*.
>>
>> Again, where is that documented?
Benjamin> Read the kernel. Notifiers are called from all sorts of hot
Benjamin> paths, so they damned well better be light.
Ben,
There' plenty of cases where adding a new notifier chain will be
preferred to adding a long list of if (foo) call() items. One place is
the fork()/exit() path for more system accounting. Being able to sleep
in those places is needed. Fortunately one can do them lock free as
they are in task context, but you need to be able to kmalloc() there.
Cheers,
Jes
next prev parent reply other threads:[~2006-01-19 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 16:34 Alan Stern
2006-01-18 18:19 ` Benjamin LaHaise
2006-01-18 20:23 ` Alan Stern
2006-01-18 21:42 ` Benjamin LaHaise
2006-01-18 21:57 ` Alan Stern
2006-01-18 22:00 ` David S. Miller
2006-01-18 22:04 ` Alan Stern
2006-01-18 23:06 ` Alan Cox
2006-01-19 3:33 ` Alan Stern
2006-01-18 22:01 ` Benjamin LaHaise
2006-01-18 22:09 ` Alan Stern
2006-01-18 22:15 ` Benjamin LaHaise
2006-01-19 10:01 ` Jes Sorensen [this message]
2006-01-18 22:18 ` David S. Miller
2006-01-18 22:18 ` Benjamin LaHaise
2006-01-18 23:07 ` Alan Cox
2006-01-19 9:55 ` Jes Sorensen
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=yq0mzhs7czp.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sekharan@us.ibm.com \
--cc=stern@rowland.harvard.edu \
/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®