From: RobertS@visi.com (RobertS)
To: linux-mtd@lists.infradead.org
Subject: 2.4.19 rmk4 Jffs2 Performance problems, Upgrade diffulculty.
Date: Tue, 11 Mar 2003 17:00:20 -0500 [thread overview]
Message-ID: <3E6E5C74.2080201@visi.com> (raw)
In-Reply-To: 200303111555.47644.tglx@linutronix.de
Thomas Gleixner wrote:
>On Tuesday 11 March 2003 13:31, RobertS wrote:
>
>
>> Please provide the name and location of the MTD snap shot so I use
>>the correct one. The mtd snapshot that I used originally was
>>mtd-snapshot-20030305.tar.gz. I had numerous problems with this snap
>>shot and 2.4.19. Unfortunately, there was a lot of "pilot" error when I
>>started this upgrade effort. Let me know and I will proceed carefully
>>and capture the results.
>>
>>
>cvs -d :pserver:anoncvs at cvs.infradead.org:/home/cvs login (password: anoncvs)
>cvs -d :pserver:anoncvs at cvs.infradead.org:/home/cvs co mtd
>
>
>
>> The performance of approximately 4 minutes to copy a 1 meg file was
>>with an almost "pristine" 2.4.19 rmk4 kernel. Does this meet
>>expectations for that iteration of jffs2?
>>
>>
>I'va never seen such long times
>
>
>
The update and build went smoothly. Unfortunately, I still oops in
exactly the same manner.
What I am doing now is turning on the verbose debug messages and keep
everything as simple as possible. I will be performing a series of
tests and will use this thread either to post my findings or further
questions.
RobertS.
next prev parent reply other threads:[~2003-03-11 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 22:56 2.4.19 rmk4 Jffs2 Performance problems, Upgrade diffulculty RobertS
2003-03-11 8:15 ` Thomas Gleixner
2003-03-11 12:31 ` RobertS
2003-03-11 14:55 ` Thomas Gleixner
2003-03-11 22:00 ` RobertS [this message]
2003-03-12 8:46 ` Thomas Gleixner
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=3E6E5C74.2080201@visi.com \
--to=roberts@visi.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 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.