@@ -264,8 +264,23 @@ static unsigned long g_completion_nsec = 10000;
module_param_named(completion_nsec, g_completion_nsec, ulong, 0444);
MODULE_PARM_DESC(completion_nsec, "Time in ns to complete a request in hardware. Default: 10,000ns");
+static int null_set_hw_queue_depth(const char *s, const struct kernel_param *kp)
+{
+ int ret;
+
+ ret = null_param_store_int(s, kp->arg, 1, INT_MAX);
+ if (ret)
+ pr_err("only positive values are allowed for queue_depth\n");
+ return ret;
+}
+
+static const struct kernel_param_ops null_hw_qdepth_param_ops = {
+ .set = null_set_hw_queue_depth,
+ .get = param_get_int,
+};
+
static int g_hw_queue_depth = 64;
-module_param_named(hw_queue_depth, g_hw_queue_depth, int, 0444);
+device_param_cb(hw_queue_depth, &null_hw_qdepth_param_ops, &g_hw_queue_depth, 0444);
MODULE_PARM_DESC(hw_queue_depth, "Queue depth for each hardware queue. Default: 64");
static bool g_use_per_node_hctx;
Right now we don't check for valid module parameter value for queue depth, that allows user to set negative values. Add a callback to error out when queue depth value is set < 1 before module is loaded. Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com> --- drivers/block/null_blk/main.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)