public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux_udf@hpesjro.fc.hp.com
Subject: Re: zeroes read back more often than appended
Date: 07 Oct 2003 14:54:37 -0600	[thread overview]
Message-ID: <1065560077.3220.1.camel@patehci2> (raw)
In-Reply-To: <1065553341.8172.45.camel@patehci2>

I first saw udf.ko of loop.ko read more zeroes than appended in RedHat
2.6.0-test6 on one pc described by dmesg as:
495MB LOWMEM available.
CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
CPU1: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
..... host bus clock speed is 199.0492 MHz.

I intend to try a number of 2.6 pc's, to see if I get consistent
results.

But initially just now, I thought I should mention, I see correct '\xAA'
read back, no troublesome zeroes, in Knoppix 2.4.22-xfs on a third pc,
in 30..90 s/test, with a loop on ext2, on one pc described by dmesg as:
255MB LOWMEM available.
Detected 866.394 MHz processor.
CPU0: Intel Pentium III (Coppermine) stepping 03
..... host bus clock speed is 133.2875 MHz.

As I repeated this test, I regretfully noticed that my original
instructions did not explicitly include such further hints as:

sudo mkdir /mnt/loop0

# visit http://sourceforge.net/projects/linux-udf/
cp -ip udftools-1.0.0b2/mkudffs/mkudffs ~/bin

Also machines with less calloc'able virtual memory and/or low quotas
can't demo that a single fwrite reads more zeroes than appended:

udfwh mkudffs 0x7800000 0x1
udfwh mkudffs 0xFFFFFFF 0x1

Instead because of those limits on such machines we can only repeat the
themultiple fwrite tests e.g.

udfwh mkudffs 0xFFFFFF 0xB
udfwh mkudffs 0xFFFF 0xC00

Pat LaVarre



  reply	other threads:[~2003-10-07 20:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 19:02 zeroes read back more often than appended Pat LaVarre
2003-10-07 20:54 ` Pat LaVarre [this message]
2003-10-08  3:49 ` Ben Fennema
2003-10-08 16:41   ` Pat LaVarre
2003-10-08 16:47     ` editable udf metadata Pat LaVarre
2003-10-08 17:51       ` Pat LaVarre
2003-10-08 18:09         ` big-endian udfct_1_0r2 Pat LaVarre
2003-10-08 18:30           ` Matthew Wilcox
     [not found]             ` <3F8472FE.9040403@lougher.demon.co.uk>
2003-10-08 19:49               ` Matthew Wilcox
2003-10-08 20:43             ` Phillip Lougher
2003-10-21 21:54         ` editable udf metadata Pat LaVarre
2003-10-21 23:17           ` Pat LaVarre
2003-10-23 16:06             ` Pat LaVarre
2003-10-24 21:40               ` Pat LaVarre
2003-10-22  8:15           ` same page access Mark B
2003-10-22 11:21             ` Matthew Wilcox
2003-10-22 17:09               ` Mark B
2003-10-22 17:10                 ` Matthew Wilcox
2003-10-08 17:02     ` zeroes read back more often than appended Pat LaVarre
2003-10-08 17:06       ` toggling smp clears x86_mce_p4thermal of make xconfig Pat LaVarre
2003-10-08 17:21     ` zeroes read back more often than appended Pat LaVarre
2003-10-08 16:46   ` soft trace of read/write of drivers/block/loop.c Pat LaVarre
2003-10-08 20:32   ` zeroes read back more often than appended Pat LaVarre
2003-10-09 20:54   ` Pat LaVarre
2003-10-10  0:52     ` Pat LaVarre
2003-10-10 16:39       ` Pat LaVarre
2003-10-10 18:15         ` Pat LaVarre
2003-10-14  0:38           ` Pat LaVarre
2003-10-14  1:48             ` Pat LaVarre
2003-10-20 23:20               ` Pat LaVarre
2003-10-21 14:47                 ` Pat LaVarre
2003-10-21 16:46                   ` Pat LaVarre
2003-10-21 18:44                     ` Pat LaVarre
2003-10-23 18:52                     ` Pat LaVarre
2003-10-27 21:55                       ` Pat LaVarre
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 16:41 Pat LaVarre
2003-11-27  0:45 ` Pat LaVarre
2003-11-28 18:20   ` Pat LaVarre
2003-11-28 18:29     ` Pat LaVarre
2003-12-11 18:42 Pat LaVarre

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=1065560077.3220.1.camel@patehci2 \
    --to=p.lavarre@ieee.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux_udf@hpesjro.fc.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox