Re: FATSystem "BUG"?



A few questions about your configuration:

1) What version of the OS are you using?
2) What kind of device are you performing those measurements on?
3) What are your cache configurations? Are you using diskcache.dll? How big
is the cache?

You can get the cache information from the registry:

HKLM\System\StorageManager\FATFS

Thank You!

--Vadim Yushprakh

"eddie" <eddiehehe@xxxxxxxxxxx> wrote in message
news:%23iAL0NHrGHA.4192@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have written some block device drivers, such as CF card, SD card, IDE
disk...There is a common problem.
For example, in CF card driver, I used the stream interface(XXX_init,
XXX_IoControl...). And I called the AdvertiseInterface() function to
declare it's a block device. So with the FAT system, we could see the
mounted disk in "My device" under WinCE. Then I copied files in & out of
the disk to test the W/R speed. I found that the write-in speed is
900KB/s, but the read-out speed is no more than 500KB/s. That's
insufferable.
I wrote an application to test R/W speed of CF card keep away from FAT: I
called CreateFile() to get the handle of the driver, then used
DeviceIocontrol() to write data in and read out. In this case, the Write
speed is 1.1MB/s, and the Read speed is more than 2MB/s.
And the same situation was appeared in SD card. With FAT: Write 1.2MB/s,
Read 500KB/s. Without FAT: Write 1.4MB/s, Read 4.1MB/s.
Even in the Ram Disk driver, the one used memory space as the virtual
storage space, the test result was: With FAT: Write more than 1.5MB/s,
Read 600KB/s. With out FAT: all very fast speed.
So I thought the FAT system may cause the low efficiency of read operation
under WinCE.
Any suggestion is helpful and thankful.



.



Relevant Pages

  • Re: [RFC] MTD driver for MMC cards
    ... A bit of a niche area, but as long as this driver doesn't look like high maintenance then it could be enough. ... limiting the number of writes to the FAT ... make sure clusters are aligned with erase blocks. ... More important is that the card can only be set to one block size at any given time. ...
    (Linux-Kernel)
  • Re: Soundblaster 16 and kernel 2.6
    ... >> The driver is present in the indicated directory. ... > info about your card, most of all the IO, IRQ and DMA values, e.g. ... > I don't know the configuration of your card. ... I should have included attribution, now that you point it out. ...
    (comp.os.linux.setup)
  • Re: FATSystem "BUG"?
    ... Are you using the same transfer size in your block driver and filesystem ... 2)Such as CF card, SD card... ... mounted disk in "My device" under WinCE. ... I wrote an application to test R/W speed of CF card keep away from FAT: ...
    (microsoft.public.windowsce.embedded)
  • [PATCH 1/3] to Documentation/digiboard.txt
    ... Remove obsolete Documentation/digiboard.txt file - driver was obsoleted ... -The Linux Digiboard Driver ... -memory base address of the Nth card, ... -Boot-time configuration when linked into the kernel ...
    (Linux-Kernel)
  • FATSystem "BUG"?
    ... I have written some block device drivers, such as CF card, SD card, IDE ... For example, in CF card driver, I used the stream interface(XXX_init, ... I wrote an application to test R/W speed of CF card keep away from FAT: ...
    (microsoft.public.windowsce.platbuilder)