From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: "Artur Piechocki" <artur.piechocki@open-e.com>,
"Łukasz Oleś" <lukasz.oles@open-e.com>
Subject: Re: xfsprogs 2.x vs 3.x logsize changed
Date: Wed, 17 Nov 2010 22:22:43 +0100 [thread overview]
Message-ID: <201011172222.44758@zmi.at> (raw)
In-Reply-To: <201011171549.04806.lukasz.oles@open-e.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 809 bytes --]
On Mittwoch, 17. November 2010 Łukasz Oleś wrote:
> Can I stay with the old log size or maybe there are some good reasons
> to use new values?
I believe the new defaults are there because it results in faster
metadata operations when there are lots of them. I'd guess if you only
ever have one writer it wouldn't matter much, but in case you have
several parallel writers it could make a difference. But I'm not a dev,
maybe they can confirm or clarify.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-17 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 14:49 xfsprogs 2.x vs 3.x logsize changed Łukasz Oleś
2010-11-17 21:22 ` Michael Monnerie [this message]
[not found] ` <4CE41315.8070402@sandeen.net>
2010-11-18 9:49 ` Łukasz Oleś
2010-11-18 14:39 ` Eric Sandeen
2010-11-19 1:04 ` Dave Chinner
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=201011172222.44758@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=artur.piechocki@open-e.com \
--cc=lukasz.oles@open-e.com \
--cc=xfs@oss.sgi.com \
/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