From: Selwyn Tang <selwyn@hectrix.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: high cpu usage using nftl for DOC2000
Date: Wed, 08 Oct 2003 18:16:06 +0800 [thread overview]
Message-ID: <3F83E3E6.3070308@hectrix.com> (raw)
In-Reply-To: <1065607132.22298.88.camel@hades.cambridge.redhat.com>
On 10/08/2003 05:58 PM, David Woodhouse wrote:
> Can you throw printk statements into various routines in nftlcore.c so
> we can it actually thinks it's doing?
I will try my best to do that later.
> You _are_ mounting your file system with -onoatime, aren't you?
I compiled in the driver to the kernel and set fstab with the line:
/dev/nftla1 /mnt/doc auto defaults 0 0
What do you mean by -onoatime? Should I change "defaults" to "noatime"?
Selwyn
next prev parent reply other threads:[~2003-10-08 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 6:54 high cpu usage using nftl for DOC2000 edward jose
2003-10-03 2:07 ` Selwyn Tang
2003-10-03 5:54 ` David Woodhouse
2003-10-03 8:22 ` Selwyn Tang
2003-10-03 8:52 ` David Woodhouse
2003-10-08 9:46 ` Selwyn Tang
2003-10-08 9:58 ` David Woodhouse
2003-10-08 10:16 ` Selwyn Tang [this message]
2003-10-08 10:22 ` David Woodhouse
2003-10-09 3:54 ` Selwyn Tang
2003-10-09 6:30 ` 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=3F83E3E6.3070308@hectrix.com \
--to=selwyn@hectrix.com \
--cc=dwmw2@infradead.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