public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Theodore Ts'o <tytso@mit.edu>, Mingming Cao <cmm@us.ibm.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Patch queue update
Date: Thu, 24 Jan 2008 09:26:56 -0700	[thread overview]
Message-ID: <20080124162656.GJ18433@webber.adilger.int> (raw)
In-Reply-To: <20080124145051.GC14348@skywalker>

On Jan 24, 2008  20:20 +0530, Aneesh Kumar K.V wrote:
> @@ -89,6 +89,8 @@ When mounting an ext4 filesystem, the following option are accepted:
>  extents			ext4 will use extents to address file data.  The
>  			file system will no longer be mountable by ext3.
>  
> +noextents		ext4 will not use extents for new files created.
> +

s/new files created/newly created files/

>  journal_checksum	Enable checksumming of the journal transactions.
>  			This will allow the recovery code in e2fsck and the
>  			kernel to detect corruption in the kernel.  It is a
> @@ -206,6 +208,10 @@ nobh			(a) cache disk block mapping information
>  			"nobh" option tries to avoid associating buffer
>  			heads (supported only for "writeback" mode).
>  
> +mballoc		(*)	Use the mutliblock allocator for block allocation
> +nomballoc		disabled multiblock allocator for block allocation.
> +stripe=n		filesystem blocks per stripe for a RAID configuration.

Please provide a more verbose description of what a "stripe" is, since the
RAID terminology is sadly vague.  Something like "number of filesystem blocks 
that mballoc will try to use for allocation size and alignment.  For RAID5/6
systems this should be the number of data disks * number of filesystem blocks
per data disk."


> @@ -3948,9 +3942,8 @@ repeat:
>  			spin_unlock(&pa->pa_lock);
>  			spin_unlock(&ei->i_prealloc_lock);
>  			printk(KERN_ERR "uh-oh! used pa while discarding\n");
> -			dump_stack();
> -			current->state = TASK_UNINTERRUPTIBLE;
> -			schedule_timeout(HZ);
> +			WARN_ON(1);

This printk and dump stack can just go away, we have removed it from our
mballoc patch as well because it was only needed for determining how often
this condition is hit and is otherwise useless.

> @@ -577,14 +529,12 @@ err_out:
>  	 *
>  	 * FIXME!! we may be touching bitmaps in different block groups.
>  	 */
> -
>  	if (ext4_journal_extend(handle,
>  			4 + 2*EXT4_QUOTA_TRANS_BLOCKS(inode->i_sb)) != 0) {
>  
>  		ext4_journal_restart(handle,
>  				4 + 2*EXT4_QUOTA_TRANS_BLOCKS(inode->i_sb));
>  	}
> -

There don't actually need to be braces here either.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

  reply	other threads:[~2008-01-24 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 14:50 Patch queue update Aneesh Kumar K.V
2008-01-24 16:26 ` Andreas Dilger [this message]
2008-01-24 16:32   ` Eric Sandeen
2008-01-24 19:50 ` Mingming Cao
  -- strict thread matches above, loose matches on Subject: below --
2008-06-15 17:21 Aneesh Kumar K.V
2008-06-16 17:49 ` Aneesh Kumar K.V
2008-06-16 22:03   ` Mingming
2008-01-10 15:33 patch " Aneesh Kumar K.V
2008-01-10 21:43 ` Andreas Dilger
2008-01-11  4:09   ` Aneesh Kumar K.V
2007-12-24  6:30 Patch " Aneesh Kumar K.V

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=20080124162656.GJ18433@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.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