From: David Woodhouse <dwmw2@infradead.org>
To: kira brown <kira@hex.linuxgrrls.org>
Cc: Herman Oosthuysen <herman@wirelessnetworksinc.com>,
"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: DiskOnChip write performance
Date: Thu, 06 Sep 2001 16:55:32 +0100 [thread overview]
Message-ID: <14482.999791732@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109061649230.9437-100000@hex.linuxgrrls.org>
kira@hex.linuxgrrls.org said:
> There are basically two ways to speed this situation up:
Don't forget "don't use O(n^3) algorithms when trying to find a new block
to write to".
--
dwmw2
next prev parent reply other threads:[~2001-09-06 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 15:01 DiskOnChip write performance Holger Friedrich
2001-09-06 15:02 ` David Woodhouse
2001-09-07 1:02 ` Ollie Lho
2001-09-06 15:05 ` kira brown
2001-09-06 15:45 ` Herman Oosthuysen
2001-09-06 15:49 ` David Woodhouse
2001-09-06 16:45 ` Herman Oosthuysen
2001-09-06 15:52 ` kira brown
2001-09-06 15:55 ` David Woodhouse [this message]
2001-09-07 0:59 ` Ollie Lho
2001-09-07 7:12 ` Bjorn Eriksson
2001-09-07 8:08 ` David Woodhouse
2001-09-07 9:49 ` Ollie Lho
2001-09-07 10:01 ` David Woodhouse
2001-09-06 15:59 ` David Woodhouse
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=14482.999791732@redhat.com \
--to=dwmw2@infradead.org \
--cc=herman@wirelessnetworksinc.com \
--cc=kira@hex.linuxgrrls.org \
--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