From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Greg KH <greg@kroah.com>
Cc: Christian Borntraeger <CBORNTRA@de.ibm.com>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Patrick Mochel <mochel@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [RFC 0/6] Backing Store for sysfs
Date: Mon, 06 Oct 2003 11:38:25 -0700 [thread overview]
Message-ID: <3F81B6A1.4030406@backtobasicsmgmt.com> (raw)
In-Reply-To: <20031006183056.GA4714@kroah.com>
Greg KH wrote:
> They might, depending on the patch implementation. And no, the issue
> isn't different, as we have to show the memory usage after all kobjects
> are accessed in sysfs from userspace, not just before, like some of the
> measurements are, in order to try to compare apples to apples.
>
My point in saying that they are different was that your original
message implied each hotplug event would be walking most (or all) of
the sysfs tree _each time_, thus effectively touching all the dentries
and inodes in the cache. In actuality during system startup it will
appear that this is the case as all the hotplug events occur, but once
that flurry is over the caches can release the unused entries. Later
hotplug events would only bring in the entries relevant to the
specific kobject that the event relates to, so would cause minimal
cache pressure.
Now that I understand how you're expecting hotplug/udev to interact
I'll bow out of this thread... I can't even begin to understand the
complexities of the patch that's been posted :-)
next prev parent reply other threads:[~2003-10-06 18:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 17:38 [RFC 0/6] Backing Store for sysfs Christian Borntraeger
2003-10-06 17:41 ` Greg KH
2003-10-06 18:00 ` Kevin P. Fleming
2003-10-06 18:11 ` Greg KH
2003-10-06 18:23 ` Kevin P. Fleming
2003-10-06 18:30 ` Greg KH
2003-10-06 18:38 ` Kevin P. Fleming [this message]
2003-10-07 8:30 ` Maneesh Soni
[not found] <Dzxw.1wW.3@gated-at.bofh.it>
[not found] ` <DGfG.4UY.3@gated-at.bofh.it>
[not found] ` <DHv1.5Ir.1@gated-at.bofh.it>
[not found] ` <DHEU.7ET.19@gated-at.bofh.it>
[not found] ` <DHY6.3c0.7@gated-at.bofh.it>
[not found] ` <DI7S.58w.13@gated-at.bofh.it>
2003-10-06 19:01 ` Pascal Schmidt
2003-10-06 19:10 ` Greg KH
2003-10-07 0:15 ` Pascal Schmidt
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 18:19 Christian Borntraeger
2003-10-06 12:34 Christian Borntraeger
2003-10-06 8:59 Maneesh Soni
2003-10-06 16:08 ` Greg KH
2003-10-06 17:31 ` Dipankar Sarma
2003-10-06 17:38 ` Greg KH
2003-10-06 18:01 ` Dipankar Sarma
2003-10-06 18:09 ` Greg KH
2003-10-06 18:31 ` Dipankar Sarma
2003-10-06 18:34 ` Greg KH
2003-10-07 9:08 ` Andreas Jellinghaus
2003-10-06 18:44 ` Patrick Mochel
2003-10-06 19:27 ` Dipankar Sarma
2003-10-06 19:30 ` viro
2003-10-06 20:01 ` Dipankar Sarma
2003-10-06 20:34 ` viro
2003-10-07 4:47 ` Maneesh Soni
2003-10-06 19:33 ` Patrick Mochel
2003-10-06 20:26 ` Dipankar Sarma
2003-10-06 20:29 ` Patrick Mochel
2003-10-07 4:31 ` Maneesh Soni
2003-10-07 5:25 ` Nick Piggin
2003-10-07 7:17 ` Maneesh Soni
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=3F81B6A1.4030406@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=CBORNTRA@de.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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