summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-02-03 09:42:39 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-03-27 00:22:46 +0100
commitcca84b569ebe3372b28949e00b0a3a17f87e2970 (patch)
tree6625a62001e9a58f6cebd7121423e245ed8bc7bd /virt/kvm
parentcd1986a3c111f7ed597619705290fa52a975014f (diff)
downloadop-kernel-dev-cca84b569ebe3372b28949e00b0a3a17f87e2970.zip
op-kernel-dev-cca84b569ebe3372b28949e00b0a3a17f87e2970.tar.gz
mtd: doc2001: initialize writebufsize
The writebufsize concept was introduce by commit "0e4ca7e mtd: add writebufsize field to mtd_info struct" and it represents the maximum amount of data the device writes to the media at a time. This is an important parameter for UBIFS which is used during recovery and which basically defines how big a corruption caused by a power cut can be. Set it to be equivalent to mtd->writesize because this is the maximum amount of data the driver writes at a time. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Cc: stable@kernel.org [2.6.38+] Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud