aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/usbip
diff options
context:
space:
mode:
authorNitin Gupta <ngupta@vflare.org>2010-08-09 22:56:48 +0530
committerGreg Kroah-Hartman <gregkh@suse.de>2010-08-31 15:36:36 -0700
commit484875adbc473041b7cf4ef0cb3f56a2ae44a448 (patch)
tree803fcaee49e52441fe3812f49e11d004769eccbf /drivers/staging/usbip
parente98419c23b1a189c932775f7833e94cb5230a16b (diff)
downloadkernel_samsung_smdk4412-484875adbc473041b7cf4ef0cb3f56a2ae44a448.zip
kernel_samsung_smdk4412-484875adbc473041b7cf4ef0cb3f56a2ae44a448.tar.gz
kernel_samsung_smdk4412-484875adbc473041b7cf4ef0cb3f56a2ae44a448.tar.bz2
Staging: zram: Remove need for explicit device initialization
Currently, the user has to explicitly write a positive value to initstate sysfs node before the device can be used. This event triggers allocation of per-device metadata like memory pool, table array and so on. We do not pre-initialize all zram devices since the 'table' array, mapping disk blocks to compressed chunks, takes considerable amount of memory (8 bytes per page). So, pre-initializing all devices will be quite wasteful if only few or none of the devices are actually used. This explicit device initialization from user is an odd requirement and can be easily avoided. We now initialize the device when first write is done to the device. Signed-off-by: Nitin Gupta <ngupta@vflare.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/staging/usbip')
0 files changed, 0 insertions, 0 deletions