From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <vipin@embeddedlinuxworks.com>
Cc: Frederic Giasson <fgiasson@mediatrix.com>,
"MTD mailing list (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 is broken
Date: Tue, 14 Aug 2001 01:00:17 +0100 [thread overview]
Message-ID: <17795.997747217@redhat.com> (raw)
In-Reply-To: <5.1.0.14.0.20010813172206.00b02a38@mail.spewey.com>
vipin@embeddedlinuxworks.com said:
> David once mentioned that there are some obvious optimizations that
> can be carried out in the JFFS2 code. Maybe he could list out his
> favorite ones and maybe someone could volunteer to tackle them one by
> one.
I committed the cleanup to jffs2_remove_node_refs_from_ino_list() (Christ,
did I name that function?), which showed up near the top of the profiles
you did. What's next? ISTR we got strange data from the profiling.
--
dwmw2
next prev parent reply other threads:[~2001-08-13 23:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F1BED55F35F4D3118C0F00E0295CFF4D9955F7@webmail.mediatrix.c om>
2001-08-13 22:27 ` JFFS2 is broken Vipin Malik
2001-08-14 0:00 ` David Woodhouse [this message]
2001-08-14 2:39 ` Vipin Malik
2001-08-15 15:09 Frederic Giasson
[not found] <F1BED55F35F4D3118C0F00E0295CFF4DD0DAE1@webmail.mediatrix.c om>
2001-08-14 21:57 ` Vipin Malik
[not found] <F1BED55F35F4D3118C0F00E0295CFF4DD0DADF@webmail.mediatrix.c om>
2001-08-14 17:57 ` Vipin Malik
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 17:57 Frederic Giasson
2001-08-14 17:39 Frederic Giasson
2001-08-14 16:46 Frederic Giasson
2001-08-13 18:34 Frederic Giasson
2001-06-29 0:14 Vipin Malik
2001-06-29 2:32 ` Nicolas Pitre
2001-06-29 9:00 ` Alan Cox
2001-06-29 14:13 ` Vipin Malik
2001-07-01 19:10 ` David Woodhouse
2001-06-29 22:11 ` Vipin Malik
2001-08-09 17:00 ` A. Craig West
2001-08-09 22:36 ` Vipin Malik
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=17795.997747217@redhat.com \
--to=dwmw2@infradead.org \
--cc=fgiasson@mediatrix.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vipin@embeddedlinuxworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.