From: Jan Kara <jack@suse.cz>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Jan Kara <jack@suse.cz>, Andreas Dilger <adilger@dilger.ca>,
linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] ext4: remove deprecated oldalloc
Date: Tue, 16 Aug 2011 15:26:27 +0200 [thread overview]
Message-ID: <20110816132627.GC23416@quack.suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.1108161035540.3675@dhcp-27-109.brq.redhat.com>
On Tue 16-08-11 10:40:12, Lukas Czerner wrote:
> On Mon, 15 Aug 2011, Jan Kara wrote:
>
> > On Mon 15-08-11 17:50:53, Lukas Czerner wrote:
> > > On Mon, 15 Aug 2011, Jan Kara wrote:
> > > > On Mon 15-08-11 16:21:27, Lukas Czerner wrote:
> > > > > On Thu, 11 Aug 2011, Andreas Dilger wrote:
> > > > > > On 2011-08-11, at 8:58 AM, Lukas Czerner wrote:
> > > > > > > On Tue, 7 Jun 2011, Lukas Czerner wrote:
> > > > > > >> For a long time now orlov is the default block allocator in the ext4. It
> > > > > > >> performs better than the old one and no one seems to claim otherwise so
> > > > > > >> we can safely drop it and make oldalloc and orlov mount option
> > > > > > >> deprecated.
> > > > > > >>
> > > > > > >> This is a part of the effort to reduce number of ext4 options hence the
> > > > > > >> test matrix.
> > > > > > >>
> > > > > > >> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> > > > > > >
> > > > > > > ping
> > > > > >
> > > > > > I'm OK with removing this, I don't think anyone uses it, and it has almost
> > > > > > no meaning with flex_bg anyway.
> > > > > >
> > > > > > That said, "orlov" is also mostly meaningless with flex_bg as well, since
> > > > > > there is very little real benefit/affinity from inodes being "close" to
> > > > > > their data blocks. We gain far more benefit from keeping the inodes
> > > > > > together than spreading them out and keeping them close to the data blocks.
> > > > >
> > > > > What about removing it for ext3 as well ? I can prepare a patch.
> > > > OK, let's start warning the option is deprecated and will be removed from
> > > > ext3. We can remove it after 2-3 releases...
> > >
> > > Is that really necessary ? It is not like we are removing a feature which
> > > would not work anymore.
> > Well, we are removing a mount option so if someone is using it e.g. in
> > /etc/fstab, his machine will fail to mount the filesystem. Or did I
> > misunderstood your intention?
>
> It will not fail to boot, see the patch at the beginning of the thread.
> It will just print KERN_WARNING that we are ignoring this option. Since
> we are not removing a feature that will be missing, we can do that. Also
> note that this is the same thing what we have done to nobh option, and
> there are probably even other examples.
Ah, OK. That would be fine I guess. I can take such patch.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-08-16 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 13:35 [PATCH] ext4: remove deprecated oldalloc Lukas Czerner
2011-06-07 14:50 ` Eric Sandeen
2011-06-07 14:53 ` Eric Sandeen
2011-06-07 15:29 ` Lukas Czerner
2011-06-08 11:01 ` Lukas Czerner
2011-08-11 14:58 ` Lukas Czerner
2011-08-11 21:05 ` Andreas Dilger
2011-08-15 14:21 ` Lukas Czerner
2011-08-15 15:27 ` Jan Kara
2011-08-15 15:50 ` Lukas Czerner
2011-08-15 18:49 ` Jan Kara
2011-08-16 8:40 ` Lukas Czerner
2011-08-16 13:26 ` Jan Kara [this message]
2011-10-08 18:09 ` Ted Ts'o
2011-09-01 8:41 ` Lukas Czerner
2011-10-05 14:32 ` Lukas Czerner
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=20110816132627.GC23416@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).