public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, webmaster@cyberdogtech.com
Subject: Re: [PATCH] Unify CONFIG_LBD and CONFIG_LSF handling
Date: Tue, 20 Jun 2006 08:52:34 -0600	[thread overview]
Message-ID: <20060620145234.GK1630@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606201616430.17704@scrub.home>

On Tue, Jun 20, 2006 at 04:20:53PM +0200, Roman Zippel wrote:
> Hi,
> 
> On Mon, 19 Jun 2006, Matthew Wilcox wrote:
> >  config LSF
> >  	bool "Support for Large Single Files"
> > -	depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
> > +	depends on !64BIT
> >  	help
> >  	  Say Y here if you want to be able to handle very large files (bigger
> >  	  than 2TB), otherwise say N.
> 
> While you're at it, could you please take care of bug #6719 and fix the 
> LSF help text?
> Thanks.

I don't really understand the complaint.  If <rare condition applies>,
say Y, otherwise say N.  If unsure, say Y.  The default is N.  Perhaps
all that's needed is to spell out the implications of saying Y?  How
about:

	  This option allows 32-bit systems to support files larger than
	  2 Terabytes, at a cost of increased kernel memory usage.  Most
	  people do not need the overhead and should answer N to this
	  question, but if you do not understand this question, answering
	  Y is safest.

Or is that too verbose?

NB: Anyone suggesting that we should say "Tibibytes" instead of
Terabytes there will be hunted down and brutally slain.  That is all.

  reply	other threads:[~2006-06-20 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 22:16 [PATCH] Unify CONFIG_LBD and CONFIG_LSF handling Matthew Wilcox
2006-06-20 14:20 ` Roman Zippel
2006-06-20 14:52   ` Matthew Wilcox [this message]
2006-06-20 15:44     ` Roman Zippel
2006-06-20 15:53       ` Matt LaPlante
2006-06-20 16:01         ` Matthew Wilcox
2006-06-20 16:12           ` Roman Zippel
2006-06-20 16:48             ` Matthew Wilcox
2006-06-20 15:59       ` Arjan van de Ven
2006-06-22  0:11         ` Matt LaPlante

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=20060620145234.GK1630@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=webmaster@cyberdogtech.com \
    --cc=zippel@linux-m68k.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