From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: symlinks in /proc/device-tree
Date: Mon, 30 May 2005 15:07:00 +1000 [thread overview]
Message-ID: <1117429620.5228.38.camel@gaston> (raw)
Hi !
Is anybody actually using one of these things in /proc/device-tree ?
- for a node name@address, symlinks from name->node and @address->node
- the fact that we remove the @address part if address is 0
I'm considering killing both of these things for 2.6.13. That will
reduce the memory footprint of the device-tree significantly (bloat in
inode cache) and it will be a more exact representation of the actual
tree. Besides, the symlinks are not really useful in practice.
Ben.
next reply other threads:[~2005-05-30 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 5:07 Benjamin Herrenschmidt [this message]
2005-05-30 6:17 ` symlinks in /proc/device-tree Olaf Hering
2005-05-30 6:22 ` Benjamin Herrenschmidt
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=1117429620.5228.38.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).