From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <esandeen@redhat.com>
Cc: Norbert Preining <preining@logic.at>, "Ted Ts'o" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Ext4 slow on links
Date: Wed, 20 Jun 2012 14:35:39 -0500 [thread overview]
Message-ID: <4FE2260B.6090602@redhat.com> (raw)
In-Reply-To: <BA050E9A-2385-4FF9-B41A-3A25F3FF066A@redhat.com>
On 6/19/12 10:57 PM, Eric Sandeen wrote:
> On Jun 19, 2012, at 10:38 PM, Norbert Preining <preining@logic.at> wrote:
>
>> Hi Ted, hi Eric,
>>
>> thanks for the answers, here some remarks.
>>
> ...
>
>> On Di, 19 Jun 2012, Eric Sandeen wrote:
>>> As Ted said, the targets might be far-flung. If you do /bin/ls -l instead
>>> of maybe an aliased ls which stats everything to make pretty colors,
>>> is that faster?
>>
>> Might be the problem, but I saw the same with a program doing
>> opendir readdir etc, so no allias or external program involved.
>>
> Of course ls -l must stat anyway. I shouldn't compose emails so late. :).
Oh, but Zach Brown reminds me that if we stat the entries in getdents/hash
order, it's roughly random w.r.t. disk location. Newer utils will sort into
inode order, I think(?) Might be interesting to strace the ls -l and see
if it's doing it in inode order, or not.
-Eric
next prev parent reply other threads:[~2012-06-20 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 0:20 Ext4 slow on links Norbert Preining
2012-06-20 2:19 ` Ted Ts'o
2012-06-20 3:38 ` Norbert Preining
2012-06-20 3:57 ` Eric Sandeen
2012-06-20 4:01 ` Norbert Preining
2012-06-20 5:18 ` Norbert Preining
2012-06-20 14:07 ` Eric Sandeen
2012-06-20 19:35 ` Eric Sandeen [this message]
2012-06-21 2:28 ` Norbert Preining
2012-06-21 4:05 ` Eric Sandeen
2012-06-21 4:50 ` Norbert Preining
2012-06-21 5:18 ` Andreas Dilger
2012-06-21 6:55 ` Norbert Preining
2012-06-22 9:53 ` Bernd Schubert
2012-06-22 14:08 ` Ted Ts'o
2012-06-20 3:15 ` Eric Sandeen
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=4FE2260B.6090602@redhat.com \
--to=sandeen@redhat.com \
--cc=esandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=preining@logic.at \
--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;
as well as URLs for NNTP newsgroup(s).