All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Enable delalloc and mballoc by default.
Date: Wed, 24 Oct 2007 12:22:09 -0500	[thread overview]
Message-ID: <471F7F41.6080800@redhat.com> (raw)
In-Reply-To: <1193244441-10149-6-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

Aneesh Kumar K.V wrote:

> @@ -1279,6 +1280,9 @@ clear_qf_name:
>  		case Opt_delalloc:
>  			set_opt (sbi->s_mount_opt, DELALLOC);
>  			break;

If delalloc, mballoc, extents are the new defaults, is there a reason to
keep them as options?  When would you need to specify -o extents, now,
for example?  (though my brain is fuzzy today, maybe I'm missing
something)  If this were not a filesystem ending in "dev" I could see
keeping it for compatibility with existing fstabs....

> +		case Opt_nodelalloc:
> +			clear_opt (sbi->s_mount_opt, DELALLOC);
> +			break;
>  		case Opt_mballoc:
>  			set_opt(sbi->s_mount_opt, MBALLOC);
>  			break;
> @@ -1824,6 +1828,8 @@ static int ext4_fill_super (struct super_block *sb, void *data, int silent)
>  	 * User -o noextents to turn it off
>  	 */

I'd either update this comment ^^^^ or remove it, I think.

>  	set_opt(sbi->s_mount_opt, EXTENTS);
> +	set_opt(sbi->s_mount_opt, DELALLOC);
> +	set_opt(sbi->s_mount_opt, MBALLOC);
>  
>  	if (!parse_options ((char *) data, sb, &journal_inum, &journal_devnum,
>  			    NULL, 0))

  parent reply	other threads:[~2007-10-24 17:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:47 Patches for review Aneesh Kumar K.V
2007-10-24 16:47 ` Aneesh Kumar K.V
2007-10-24 16:47   ` Aneesh Kumar K.V
2007-10-24 16:47     ` [PATCH] ext4: Change the default behaviour on error Aneesh Kumar K.V
2007-10-24 16:47       ` [PATCH] ext4: Fix mballoc BUG when running compilebench Aneesh Kumar K.V
2007-10-24 16:47         ` [PATCH] ext4: Enable delalloc and mballoc by default Aneesh Kumar K.V
2007-10-24 16:47           ` [PATCH] ext4: Show mballoc and delalloc options Aneesh Kumar K.V
2007-10-24 16:47             ` [PATCH] ext4: Fix ext4_show_options to show the correct mount options Aneesh Kumar K.V
2007-10-24 17:55               ` Eric Sandeen
2007-10-24 18:18                 ` Aneesh Kumar K.V
2007-10-24 18:25                   ` Eric Sandeen
2007-10-24 17:24             ` [PATCH] ext4: Show mballoc and delalloc options Eric Sandeen
2007-10-24 17:22           ` Eric Sandeen [this message]
2007-10-24 17:30             ` [PATCH] ext4: Enable delalloc and mballoc by default Aneesh Kumar K.V
2007-10-24 19:15             ` Mingming Cao
2007-10-24 21:06             ` Andreas Dilger
2007-10-24 21:15               ` Eric Sandeen
2007-10-24 22:59                 ` Andreas Dilger

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=471F7F41.6080800@redhat.com \
    --to=sandeen@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.