From: Hugh Dickins <hugh@veritas.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org, William Irwin <wli@holomorphy.com>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH 4/5] shmem: use call_once()
Date: Tue, 11 Mar 2008 13:41:54 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0803111323130.18261@blonde.site> (raw)
In-Reply-To: <961aa3350803110529o61fe42e8q27ab10e0cb8f9bb6@mail.gmail.com>
On Tue, 11 Mar 2008, Akinobu Mita wrote:
> 2008/3/11, Hugh Dickins <hugh@veritas.com>:
> > On Tue, 11 Mar 2008, Akinobu Mita wrote:
> > > This patch defers mounting tmpfs till shmem_file_setup() is
> > > called first time by using call_once().
> >
> > Please explain why we might need this patch: is something changing
> > elsewhere? Or are you misled by that "module_init(init_tmpfs)"
> > into thinking that mm/shmem.c is sometimes built modular?
>
> If no processes call shmem_file_setup() (via shm_get(2)), it is unnecessary
or shmem_zero_setup, not very common
> to do vfs_kern_mount(&tmpfs_fs_type, ...) unconditionary in boot-time.
> So I thought it is suitable example to demonstrate how to use "call_once()"
> in this patch set.
Oh, I see, thanks. Well, I don't feel all that strongly about it; but
on the whole I'd prefer we leave it as part of the __init, than change
it around to provide this example (and risk introducing some weird issue
e.g. related to its "dev"?). I guess the same should go for the huge
and the tiny, whereas you have better justification in the idr case.
Call me over-cautious.
Hugh
prev parent reply other threads:[~2008-03-11 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080310145704.GA6396@APFDCB5C>
[not found] ` <20080310150026.GA6407@APFDCB5C>
2008-03-10 15:01 ` [PATCH 3/5] hugetlbfs: use call_once() Akinobu Mita
2008-03-10 15:03 ` [PATCH 4/5] shmem: " Akinobu Mita
2008-03-10 15:05 ` [PATCH 5/5] tiny-shmem: " Akinobu Mita
2008-03-10 22:15 ` [PATCH 4/5] shmem: " Hugh Dickins
2008-03-11 12:29 ` Akinobu Mita
2008-03-11 13:41 ` Hugh Dickins [this message]
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=Pine.LNX.4.64.0803111323130.18261@blonde.site \
--to=hugh@veritas.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).