From: Matt Mackall <mpm@selenic.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [patch 2/4] Configure out file locking features
Date: Tue, 29 Jul 2008 13:57:55 -0500 [thread overview]
Message-ID: <1217357875.15724.167.camel@calx> (raw)
In-Reply-To: <20080729181751.GA24924@parisc-linux.org>
On Tue, 2008-07-29 at 12:17 -0600, Matthew Wilcox wrote:
> On Tue, Jul 29, 2008 at 05:45:22PM +0200, Thomas Petazzoni wrote:
> > This patch adds the CONFIG_FILE_LOCKING option which allows to remove
> > support for advisory locks. With this patch enabled, the flock()
> > system call, the F_GETLK, F_SETLK and F_SETLKW operations of fcntl()
> > and NFS support are disabled. These features are not necessarly needed
> > on embedded systems. It allows to save ~11 Kb of kernel code and data:
> >
> > text data bss dec hex filename
> > 1125436 118764 212992 1457192 163c28 vmlinux.old
> > 1114299 118564 212992 1445855 160fdf vmlinux
> > -11137 -200 0 -11337 -2C49 +/-
> >
> > This patch has originally been written by Matt Mackall
> > <mpm@selenic.com>, and is part of the Linux Tiny project.
> >
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> In principle, I think this is a great idea.
>
> > config NFS_FS
> > tristate "NFS client support"
> > - depends on INET
> > + depends on INET && FILE_LOCKING
> > select LOCKD
> > select SUNRPC
> > select NFS_ACL_SUPPORT if NFS_V3_ACL
>
> I think this part is a little lazy. It should be possible to support
> NFS without file locking. I suspect that's really not in-scope for the
> linux-tiny tree as currently envisaged with the focus on embedded
> devices that probably don't use NFS anyway. Do we want to care about
> the situation of a machine with fixed workload, that doesn't need file
> locking, but does use NFS?
I would lean towards no, but if someone comes along who cares, they're
welcome to try it. This stuff all has to strike a balance between
savings and effort/complexity/maintainability, so any time the submitter
is too lazy to cover a less common use case, it's probably a good sign
they're approaching that tipping point.
On the other hand, if you think it's trivial to do a locking-ectomy on
NFS, I'd be happy to see it.
The typical embedded NFS-based devices are NAS servers and media players
and are going to be more concerned about things like page cache
balancing.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2008-07-29 18:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080729154520.728594017@free-electrons.com>
2008-07-29 15:45 ` [patch 1/4] Configure out AIO support Thomas Petazzoni
[not found] ` <20080729154747.574989775@free-electrons.com>
2008-07-29 16:27 ` Matt Mackall
[not found] ` <20080729154747.872888047@free-electrons.com>
2008-07-29 18:17 ` [patch 2/4] Configure out file locking features Matthew Wilcox
2008-07-29 18:57 ` Matt Mackall [this message]
2008-07-29 20:00 ` Jamie Lokier
2008-07-30 14:27 ` Adrian Bunk
2008-07-30 15:40 ` Thomas Petazzoni
2008-07-31 6:27 ` Uwe Kleine-König
2008-07-31 9:27 [patch 0/4] [resend] Add configuration options to disable features not needed on embedded devices Thomas Petazzoni
2008-07-31 9:27 ` [patch 2/4] Configure out file locking features Thomas Petazzoni
2008-07-31 13:53 ` Adrian Bunk
2008-07-31 14:20 ` Thomas Petazzoni
2008-07-31 15:37 ` Adrian Bunk
2008-07-31 16:26 ` Thomas Petazzoni
2008-07-31 16:49 ` Adrian Bunk
2008-07-31 16:57 ` David Woodhouse
2008-07-31 17:32 ` Tim Bird
2008-07-31 18:12 ` Robert Schwebel
2008-07-31 19:31 ` Adrian Bunk
2008-08-01 7:28 ` Robert Schwebel
2008-07-31 19:16 ` Adrian Bunk
2008-07-31 20:37 ` Tim Bird
2008-08-02 16:38 ` J. Bruce Fields
2008-08-04 13:52 ` Thomas Petazzoni
2008-08-04 18:16 ` J. Bruce Fields
2008-08-04 18:24 ` Tim Bird
2008-08-04 18:25 ` J. Bruce Fields
2008-08-04 18:54 ` Matt Mackall
2008-08-04 19:42 ` J. Bruce Fields
2008-08-04 22:32 ` Tim Bird
2008-08-06 13:12 ` Thomas Petazzoni
2008-08-07 22:55 ` J. Bruce Fields
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=1217357875.15724.167.camel@calx \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=thomas.petazzoni@free-electrons.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).