From: "Lukáš Czerner" <lczerner@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH 2/2] mke2fs: Enable lazy_itable_init on newer kernel by default
Date: Mon, 3 Mar 2014 13:53:50 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1403031353250.2258@localhost.localdomain> (raw)
In-Reply-To: <530B84B9.1040203@redhat.com>
On Mon, 24 Feb 2014, Eric Sandeen wrote:
> Date: Mon, 24 Feb 2014 11:43:21 -0600
> From: Eric Sandeen <sandeen@redhat.com>
> To: Lukas Czerner <lczerner@redhat.com>, linux-ext4@vger.kernel.org
> Cc: tytso@mit.edu
> Subject: Re: [PATCH 2/2] mke2fs: Enable lazy_itable_init on newer kernel by
> default
>
> On 2/24/14, 11:41 AM, Lukas Czerner wrote:
> > Currently is used did not specified lazy_itable_init option we rely on
>
> s/is used did not specified/if user did not specify/ :)
>
> > information from ext4 module exported via sysfs interface. However if
> > the ext4 module is not loaded it will not be enabled even though kernel
> > might support it.
> >
> > With this commit we set the default according to the kernel version,
> > however we still allow it to be set manually via extended option or be
> > enabled in case that ext4 module advertise that it supports this
> > feature.
> >
> > Signed-off-by: Lukas Czerner <lczerner@redhat.com>
>
> Thanks,
> Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Hi Ted,
are you planning to take this in ?
Thanks!
-Lukas
>
> > ---
> > misc/mke2fs.c | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/misc/mke2fs.c b/misc/mke2fs.c
> > index 957b4b6..e1c6d09 100644
> > --- a/misc/mke2fs.c
> > +++ b/misc/mke2fs.c
> > @@ -2146,7 +2146,15 @@ profile_error:
> > blocksize, sys_page_size);
> > }
> >
> > - lazy_itable_init = 0;
> > + /*
> > + * On newer kernels we do have lazy_itable_init support. So pick the
> > + * right default in case ext4 module is not loaded.
> > + */
> > + if (is_before_linux_ver(2, 6, 37))
> > + lazy_itable_init = 0;
> > + else
> > + lazy_itable_init = 1;
> > +
> > if (access("/sys/fs/ext4/features/lazy_itable_init", R_OK) == 0)
> > lazy_itable_init = 1;
> >
> >
>
>
next prev parent reply other threads:[~2014-03-03 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 17:41 [PATCH 1/2] mke2fs: Add revision to the is_before_linux_ver() Lukas Czerner
2014-02-24 17:41 ` [PATCH 2/2] mke2fs: Enable lazy_itable_init on newer kernel by default Lukas Czerner
2014-02-24 17:43 ` Eric Sandeen
2014-03-03 12:53 ` Lukáš Czerner [this message]
2014-07-06 1:09 ` Theodore Ts'o
2014-07-06 1:09 ` [PATCH 1/2] mke2fs: Add revision to the is_before_linux_ver() Theodore Ts'o
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=alpine.LFD.2.00.1403031353250.2258@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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