diff options
| author | Cyril Bur <cyril.bur@au1.ibm.com> | 2017-07-28 16:46:22 +1000 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2017-08-01 13:57:08 +1000 |
| commit | b23dd180393a99cb6e73e46b93070480f424dd1c (patch) | |
| tree | ee1e2e52e90a51e95f5986e0f7efc8779cee86cb /external | |
| parent | 151ab54126c57264fd88f41a8667b78021ca83db (diff) | |
| download | skiboot-b23dd180393a99cb6e73e46b93070480f424dd1c.zip skiboot-b23dd180393a99cb6e73e46b93070480f424dd1c.tar.gz skiboot-b23dd180393a99cb6e73e46b93070480f424dd1c.tar.bz2 | |
libflash/file: Break up MTD erase ioctl() calls
Unfortunately not all drivers are created equal and several drivers on
which pflash relies block in the kernel for quite some time and ignore
signals.
This is really only a problem if pflash is to perform large erases. So
don't, perform these ops in small chunks.
An in kernel fix is possible in most cases but it takes time and systems
will be running older drivers for quite some time. Since sector erases
aren't significantly slower than whole chip erases there isn't much of a
performance penalty to breaking up the erase ioctl()s.
Signed-off-by: Cyril Bur <cyril.bur@au1.ibm.com>
Reviewed-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'external')
0 files changed, 0 insertions, 0 deletions