From: Benno Schulenberg <bensberg@justemail.net>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: "Util-Linux" <util-linux@vger.kernel.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Update ext3/4 mount options
Date: Thu, 09 Jan 2014 21:30:55 +0100 [thread overview]
Message-ID: <1389299455.29292.68757293.7B539718@webmail.messagingengine.com> (raw)
In-Reply-To: <1389288890-17282-1-git-send-email-cmaiolino@redhat.com>
On Thu, Jan 9, 2014, at 18:34, Carlos Maiolino wrote:
> -have changed, this option allows the user to specify
> +have changed, these options allows the user to specify
s/allows/allow/
> +identified through euther its new major/minor numbers encoded
> +in devnum, or via a path to the device.
s/through euther/either through/
(swapped, otherwise the "via" needs to be dropped)
> +Abort the journal if an error occurs in a file data buffer in ordered mode.
"Abort loading the journal..." maybe?
> +The lazy itable init code will wait n times the number of milliseconds it took
> +to zero out the previous block group's inode table. This minimizes the impact on
> +the system performance while filesystem's inode table is being initialized.
s/the system/system/
s/while/while the/
> +useful in memory constrained environments, where a very large directory can
better: memory-constrained
> +cause severe performance problems or even provoke the Out Of Memory killer. (For
> +example, if there is only 512mb memory available, a 176mb directory may
> +seriously cramp the system's style).
s/)./.)/
Benno
--
http://www.fastmail.fm - Choose from over 50 domains or use your own
next prev parent reply other threads:[~2014-01-09 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 17:34 [PATCH] Update ext3/4 mount options Carlos Maiolino
2014-01-09 20:30 ` Benno Schulenberg [this message]
2014-01-10 12:57 ` Carlos Maiolino
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=1389299455.29292.68757293.7B539718@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--cc=cmaiolino@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=util-linux@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