public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: akorolev <alexey.korolev@intel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Centralized summary as a way to speed up "ls" time
Date: Tue, 10 Apr 2007 20:24:28 +0300	[thread overview]
Message-ID: <1176225868.19966.66.camel@sauron> (raw)
In-Reply-To: <461BC120.2080507@intel.com>

On Tue, 2007-04-10 at 20:53 +0400, akorolev wrote:
> Hello Ferenc,
> 
> While using JFFS2 on NAND devices with large size and many files I faced 
> the problem of very slow "ls" performance.
> On folder which contains ~40 files and ~80MB ls could take ~25sec!

One way could be to introduce an aggregated dentry node which would
store several, say 32 direntries together, instead of having
per-direntry node.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2007-04-10 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 16:53 Centralized summary as a way to speed up "ls" time akorolev
2007-04-10 17:24 ` Artem Bityutskiy [this message]
2007-04-12 12:16 ` Ferenc Havasi

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=1176225868.19966.66.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=alexey.korolev@intel.com \
    --cc=linux-mtd@lists.infradead.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