From: ebiederm@xmission.com (Eric W. Biederman)
To: Paul Jackson <pj@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, Simon.Derr@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
Date: Thu, 02 Mar 2006 09:32:45 -0700 [thread overview]
Message-ID: <m1y7zskdsi.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060302062359.5940ff7f.pj@sgi.com> (Paul Jackson's message of "Thu, 2 Mar 2006 06:23:59 -0800")
Paul Jackson <pj@sgi.com> writes:
>> Seems pointless. This just increases #ifdef churn for no gain.
>
> Take a look at fs/proc/base.c. That's how pretty much all the
> other proc hooks are done, with ifdef's around their proc hooks.
>
> ifdef minimization is a good goal, yes.
>
> But uniformity of practice is another good goal.
Agreed. However the direction I am gradually moving fs/proc/base.c
is the opposite. Moving things out of it as much as is reasonably
possible.
I already moved out all of the /proc/<pid>/?maps code into
fs/proc/task_mmu.c
I think the more important piece of uniform practice is to put all of
the operations structures and methods together in one file so that it
is easier to look between them, when making modifications especially
since cpuset_open and proc_cpuset_show are interdependent.
Eric
next prev parent reply other threads:[~2006-03-02 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 7:08 Paul Jackson
2006-03-02 8:47 ` Christoph Hellwig
2006-03-02 14:23 ` Paul Jackson
2006-03-02 16:32 ` Eric W. Biederman [this message]
2006-03-02 16:52 ` Paul Jackson
2006-03-02 17:09 ` Eric W. Biederman
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=m1y7zskdsi.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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®