summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorStefani Seibold <stefani@seibold.net>2010-04-18 22:46:44 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2010-05-10 14:22:30 +0100
commitc4e773764cead9358fd4b036d1b883fff3968513 (patch)
treeceb30e53d7ba33a071653c2bc05c06293d84575f /README
parent67026418f534045525a7c39f506006cd7fbd197f (diff)
downloadlinux-3.10-c4e773764cead9358fd4b036d1b883fff3968513.tar.gz
linux-3.10-c4e773764cead9358fd4b036d1b883fff3968513.tar.bz2
linux-3.10-c4e773764cead9358fd4b036d1b883fff3968513.zip
mtd: fix a huge latency problem in the MTD CFI and LPDDR flash drivers.
The use of a memcpy() during a spinlock operation will cause very long thread context switch delays if the flash chip bandwidth is low and the data to be copied large, because a spinlock will disable preemption. For example: A flash with 6,5 MB/s bandwidth will cause under ubifs, which request sometimes 128 KiB (the flash erase size), a preemption delay of 20 milliseconds. High priority threads will not be served during this time, regardless whether this threads access the flash or not. This behavior breaks real time. The patch changes all the use of spin_lock operations for xxxx->mutex into mutex operations, which is exact what the name says and means. I have checked the code of the drivers and there is no use of atomic pathes like interrupt or timers. The mtdoops facility will also not be used by this drivers. So it is dave to replace the spin_lock against mutex. There is no performance regression since the mutex is normally not acquired. Changelog: 06.03.2010 First release 26.03.2010 Fix mutex[1] issue and tested it for compile failure Signed-off-by: Stefani Seibold <stefani@seibold.net> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions