From: Ollie Lho <ollie@sis.com.tw>
To: David Woodhouse <dwmw2@infradead.org>
Cc: kira brown <kira@hex.linuxgrrls.org>,
Herman Oosthuysen <herman@wirelessnetworksinc.com>,
"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: DiskOnChip write performance
Date: Fri, 07 Sep 2001 17:49:22 +0800 [thread overview]
Message-ID: <3B989822.DC1D51BE@sis.com.tw> (raw)
In-Reply-To: 17891.999850127@redhat.com
David Woodhouse wrote:
>
> ollie@sis.com.tw said:
> > > Don't forget "don't use O(n^3) algorithms when trying to find a new
> > > block to write to".
>
> > What does this suppose to mean ??
>
> Algorithms which take time proportional to the cube of 'n', where n is some
> variable indicating the complexity of the task - in this case it would be
> the number of blocks on the DiskOnChip which are to be considered for
> selection.
>
Yea, I know what Big O is although I am not CompSci graduate. My
question
is which part of the NFTL code is that bad ??
Ollie
next prev parent reply other threads:[~2001-09-07 9:48 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
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 [this message]
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=3B989822.DC1D51BE@sis.com.tw \
--to=ollie@sis.com.tw \
--cc=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 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.