From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] config: Fix CONFIG_LFS option
Date: Tue, 28 Mar 2006 17:48:34 -0500 [thread overview]
Message-ID: <1143586114.8199.49.camel@lade.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603281430370.15714@g5.osdl.org>
On Tue, 2006-03-28 at 14:34 -0800, Linus Torvalds wrote:
>
> On Tue, 28 Mar 2006, Trond Myklebust wrote:
> >
> > The help text says that if you select CONFIG_LBD, then it will
> > automatically select CONFIG_LFS. Nope... That isn't currently the
> > case.
>
> I'm not sure your patch makes anything much better, though.
>
> Why does CONFIG_LSF exist in the first place? Afaik, it only affects a
> totally not-very-interesting thing (blkcnt_t) for a totally not very
> interesting feature (the number of people who want single files >2TB is
> likely not very big).
>
> Having it auto-selected by LBD sounds insane, since LBD is likely more
> interesting than LSF itsef is. It would make more sense to go the other
> way (have LSF auto-select LBD).
NFSv3 and CIFS are two examples of commonly used filesystems that don't
care a hoot for CONFIG_LBD, but that still want to be able to support
large values for inode->i_blocks.
Cheers,
Trond
prev parent reply other threads:[~2006-03-28 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 22:18 Trond Myklebust
2006-03-28 22:34 ` Linus Torvalds
2006-03-28 22:44 ` Andrew Morton
2006-03-28 22:48 ` Trond Myklebust [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=1143586114.8199.49.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®