mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Trond.Myklebust@netapp.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] config: Fix CONFIG_LFS option
Date: Tue, 28 Mar 2006 14:44:52 -0800	[thread overview]
Message-ID: <20060328144452.12812f25.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603281430370.15714@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> 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).

Yes, it's strictly a bugfix, but it's not a very big bug.  Perhaps we
should turn it on all the time and not have the config option, but it does
have some cost in text size, data size and instruction count.

> 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).

Spose so.  I wonder what distributors will choose to do.

It's a bit odd to have a config option to select whether or not to have a
buggy kernel.


  reply	other threads:[~2006-03-28 22:45 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 [this message]
2006-03-28 22:48   ` Trond Myklebust

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=20060328144452.12812f25.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Trond.Myklebust@netapp.com \
    --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®