From: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Valdis.Kletnieks@vt.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fs/Kconfig question regarding CONFIG_BLOCK
Date: Fri, 20 Oct 2006 21:14:03 -0300 [thread overview]
Message-ID: <200610210014.k9L0E3pr005019@laptop13.inf.utfsm.cl> (raw)
In-Reply-To: Message from Jens Axboe <jens.axboe@oracle.com> of "Wed, 18 Oct 2006 09:09:22 +0200." <20061018070922.GB24452@kernel.dk>
Jens Axboe <jens.axboe@oracle.com> wrote:
> On Tue, Oct 17 2006, Jan Engelhardt wrote:
> > >> Never mind, I see that some filesystems have 'depends on BLOCK' instead
> > >> of being wrapped into if BLOCK. Not really consistent but whatever.
> > >
> > >Feel free to send in patches that make things more consistent.
> >
> > How would you like things? if BLOCK or depends on BLOCK?
>
> Well, if you can hide an entire block with if BLOCK, then that would be
> preferred. Otherwise depends on BLOCK.
>
> > Does menuconfig/oldconfig/etc. parse the whole config structure faster
> > it it done either way?
>
> I'd be surprised if if BLOCK wasn't faster over, say, 10 depends on
> BLOCK.
I'd be /very/ surprised if anybody even noticed...
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513
next prev parent reply other threads:[~2006-10-21 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 18:41 Jan Engelhardt
2006-10-17 18:57 ` Valdis.Kletnieks
2006-10-17 19:21 ` Jan Engelhardt
2006-10-17 19:36 ` Jens Axboe
2006-10-17 19:47 ` Jan Engelhardt
2006-10-18 7:09 ` Jens Axboe
2006-10-18 17:56 ` Randy Dunlap
2006-10-19 12:20 ` Jens Axboe
2006-10-21 0:14 ` Horst H. von Brand [this message]
2006-10-21 0:17 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-10-17 18:38 Jan Engelhardt
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=200610210014.k9L0E3pr005019@laptop13.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jengelh@linux01.gwdg.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®