linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <nathanl@austin.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Proposal for device-tree walking semantics
Date: Tue, 24 Jun 2003 11:53:42 -0500	[thread overview]
Message-ID: <3EF88216.6010106@austin.ibm.com> (raw)


(Apologies if this doesn't get associated with the original post
correctly, the original post was forwarded to me.)

I've been looking at this issue a bit from the ppc64 side.

 > The get() function is actually more a try_get()
 > (the idea is that a remove in progress would make it fail)

Regarding removal of nodes, how might the removal of files under
/proc/device-tree be handled?  Note that the data pointers associated
with each proc entry refer to struct property's, not device_node's.
Should the struct property's have refcounts too?  Also note that
add_node() in fs/proc/proc_devtree.c creates symbolic links; I haven't
been able to come up with a pleasing solution for removing those.  It
seems to require a manual traversal of the proc_dir_entry's subdir list,
an operation during which the procfs code holds the big kernel lock
(e.g. proc_lookup()).

I agree with renaming device_node to of_node.

Nathan


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-06-24 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 16:53 Nathan Lynch [this message]
2003-06-24 23:25 ` Proposal for device-tree walking semantics Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2003-06-23 13:05 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=3EF88216.6010106@austin.ibm.com \
    --to=nathanl@austin.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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).