From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Linux/m68k" <linux-m68k@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel size increase of +256 KiB (was: Re: RPCSEC_GSS: Share all credential caches on a per-transport basis)
Date: Fri, 13 Sep 2013 08:23:54 +0200 [thread overview]
Message-ID: <CAMuHMdXz+wcjwf=ebcn3nMJhYk8mCGm2T16dcJzOGx+gN+TYTw@mail.gmail.com> (raw)
In-Reply-To: <1379017042.2627.3.camel@leira.trondhjem.org>
On Thu, Sep 12, 2013 at 10:17 PM, Myklebust, Trond
<Trond.Myklebust@netapp.com> wrote:
>> Only for the modular case. What about builtin, e.g. for nfsroot?
>>
>> Or is it better to not build in NFS_V4 support in that case?
>>
>> config NFS_V4
>> If unsure, say Y.
>>
>> config NFSD_V4
>> If unsure, say N.
>>
>> So that's why my defconfig has NFS_V4 but not NFSD_V4.
>
> It should be possible now to compile in NFSv3 support (and/or NFSv2),
> while keeping NFSv4 a module. That will usually result in
> CONFIG_SUNRPC_GSS=m...
Indeed. Making NFS_V4 modular saves 102 KiB, i.e. 2.5% of a typical
almost-4-MiB kernel image!
> Of course, if your defconfig doesn't have module support then, yes, your
> only option to avoid compiling in rpcsec_gss is to not select NFSv4 at
> all.
It has. But it needs everything to boot (block, net, nfs) as built-in.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2013-09-13 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 13:24 Kernel size increase of +256 KiB (was: Re: RPCSEC_GSS: Share all credential caches on a per-transport basis) Geert Uytterhoeven
2013-09-12 14:13 ` Myklebust, Trond
2013-09-12 19:20 ` Geert Uytterhoeven
2013-09-12 20:17 ` Myklebust, Trond
2013-09-13 6:23 ` Geert Uytterhoeven [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='CAMuHMdXz+wcjwf=ebcn3nMJhYk8mCGm2T16dcJzOGx+gN+TYTw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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).