From: Mark Lord <kernel@teksavvy.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Alex Elder <aelder@sgi.com>,
Stan Hoeppner <stan@hardwarefreak.com>
Subject: Re: xfs: very slow after mount, very slow at umount
Date: Thu, 27 Jan 2011 20:36:26 -0500 [thread overview]
Message-ID: <4D421D9A.50007@teksavvy.com> (raw)
In-Reply-To: <4D421A68.9000607@teksavvy.com>
On 11-01-27 08:22 PM, Mark Lord wrote:
> On 11-01-27 07:17 PM, Dave Chinner wrote:
>>
>> In my experience with XFS, most people who tweak mkfs parameters end
>> up with some kind of problem they can't explain and don't know how
>> to solve. And they are typically problems that would not have
>> occurred had they simply used the defaults in the first place. What
>> you've done is a perfect example of this.
>
> Maybe. But what I read from the paragraph above,
> is that the documentation could perhaps explain things better,
> and then people other than the coders might understand how
> best to tweak it.
By the way, the documentation is excellent, for a developer who
wants to work on the codebase. It describes the data structures
and layouts etc.. better than perhaps any other Linux filesystem.
But it doesn't seem to describe the algorithms, such as how it
decides where to store a recording stream.
I'm not complaining, far from it. XFS is simply wonderful,
and my DVR literally couldn't work without it.
But I am as technical as you are, and I like to experiment and
understand the technology I use. That's partly why we both work
on the Linux kernel.
Cheers
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-28 1:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D40C8D1.8090202@teksavvy.com>
2011-01-27 3:30 ` xfs: very slow after mount, very slow at umount Dave Chinner
2011-01-27 3:49 ` Mark Lord
2011-01-27 5:17 ` Stan Hoeppner
2011-01-27 15:12 ` Mark Lord
2011-01-27 15:40 ` Justin Piszcz
2011-01-27 16:03 ` Mark Lord
2011-01-27 19:40 ` Stan Hoeppner
2011-01-27 20:11 ` david
2011-01-27 23:53 ` Stan Hoeppner
2011-01-28 2:09 ` david
2011-01-28 13:56 ` Dave Chinner
2011-01-28 19:26 ` david
2011-01-29 5:40 ` Dave Chinner
2011-01-29 6:08 ` david
2011-01-29 7:35 ` Dave Chinner
2011-01-31 19:17 ` Christoph Hellwig
2011-01-27 21:56 ` Mark Lord
2011-01-28 0:17 ` Dave Chinner
2011-01-28 1:22 ` Mark Lord
2011-01-28 1:36 ` Mark Lord [this message]
2011-01-28 4:14 ` David Rees
2011-01-28 14:22 ` Mark Lord
2011-01-28 7:31 ` Dave Chinner
2011-01-28 14:33 ` Mark Lord
2011-01-28 23:58 ` Dave Chinner
2011-01-28 19:18 ` Martin Steigerwald
2011-01-27 20:24 ` John Stoffel
2011-01-27 23:41 ` Dave Chinner
2011-01-28 0:59 ` Mark Lord
2011-01-27 23:39 ` Dave Chinner
[not found] ` <4D40CDCF.4010301@teksavvy.com>
2011-01-27 3:43 ` Dave Chinner
2011-01-27 3:53 ` Mark Lord
2011-01-27 4:54 ` Mark Lord
2011-01-27 23:34 ` 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=4D421D9A.50007@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=aelder@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stan@hardwarefreak.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