From: John Zielinski <grim@undead.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] sysfs kobject that doesn't trigger hotplug events
Date: Thu, 20 May 2004 21:19:38 -0400 [thread overview]
Message-ID: <40AD592A.2070303@undead.cc> (raw)
In-Reply-To: <200405182218.20987.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> You are wasting 4 bytes for every kobject out there. Just implement your
> private hotplug callback that would return something like -ENODEV so the
> hotplug helper would not be called. If needed you can call
> kobject_hotplug
> later, when you are ready.
Actually for every kobj_type structure, not for every kobject. Doing a
quick scan through the kernel I found 25 kobj_type decelerations so that
would add up to 100 bytes only. And that could be made a byte or flags
field.
I wasn't sure if it was possible to create a subsystem that wasn't a
part of the sysfs tree that contained kobjects that were. Looking
trough the code again it looks like it is so I'll use the hotplug filter
as you suggest.
John
next prev parent reply other threads:[~2004-05-22 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 2:11 [RFC] sysfs kobject that doesn't trigger hotplug events John Zielinski
2004-05-19 3:18 ` Dmitry Torokhov
2004-05-21 1:19 ` John Zielinski [this message]
2004-05-19 3:34 ` Greg KH
2004-05-19 4:43 ` John Zielinski
2004-05-19 5:16 ` Greg KH
2004-05-22 1:38 ` John Zielinski
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=40AD592A.2070303@undead.cc \
--to=grim@undead.cc \
--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