From: Jon Mason <jdmason@kudzu.us>
To: Gary R Hook <gary.hook@amd.com>
Cc: linux-ntb@googlegroups.com, Allen.Hubbe@emc.com, dave.jiang@intel.com
Subject: Re: [PATCH V3 3/3] ntb: Add more debugfs support for ntb_perf testing options
Date: Sun, 14 May 2017 09:33:23 -0400 [thread overview]
Message-ID: <20170514133323.GB6027@kudzu.us> (raw)
In-Reply-To: <20170509143336.12995.17807.stgit@taos.amd.com>
On Tue, May 09, 2017 at 09:33:36AM -0500, Gary R Hook wrote:
> The ntb_perf tool uses module parameters to control the
> characteristics of its test. Enable the changing of these
> options through debugfs, and eliminating the need to unload
> and reload the module to make changes and run additional tests.
>
> Add a new module parameter that forces the DMA channel
> selection onto the same node as the NTB device (default: true).
>
> - seg_order: Size of the NTB memory window; power of 2.
> - run_order: Size of the data buffer; power of 2.
> - use_dma: Use DMA or memcpy? Default: 0.
> - on_node: Only use DMA channel(s) on the NTB node. Default: true.
>
>
> Signed-off-by: Gary R Hook <gary.hook@amd.com>
> ---
> drivers/ntb/test/ntb_perf.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/drivers/ntb/test/ntb_perf.c b/drivers/ntb/test/ntb_perf.c
> index 60e0dd320aef..6fdddf86269e 100644
> --- a/drivers/ntb/test/ntb_perf.c
> +++ b/drivers/ntb/test/ntb_perf.c
> @@ -737,6 +737,10 @@ static int perf_debugfs_setup(struct perf_ctx *perf)
> struct dentry *debugfs_node_dir;
> struct dentry *debugfs_run;
> struct dentry *debugfs_threads;
> + struct dentry *debugfs_seg_order;
> + struct dentry *debugfs_run_order;
> + struct dentry *debugfs_use_dma;
> + struct dentry *debugfs_on_node;
>
> if (!debugfs_initialized())
> return -ENODEV;
> @@ -764,6 +768,30 @@ static int perf_debugfs_setup(struct perf_ctx *perf)
> if (!debugfs_threads)
> return -ENODEV;
>
> + debugfs_seg_order = debugfs_create_u32("seg_order", 0600,
> + debugfs_node_dir,
> + &seg_order);
> + if (!debugfs_seg_order)
> + return -ENODEV;
> +
> + debugfs_run_order = debugfs_create_u32("run_order", 0600,
> + debugfs_node_dir,
> + &run_order);
> + if (!debugfs_run_order)
> + return -ENODEV;
> +
> + debugfs_use_dma = debugfs_create_bool("use_dma", 0600,
> + debugfs_node_dir,
> + &use_dma);
> + if (!debugfs_use_dma)
> + return -ENODEV;
> +
> + debugfs_on_node = debugfs_create_bool("on_node", 0600,
> + debugfs_node_dir,
> + &on_node);
> + if (!debugfs_on_node)
> + return -ENODEV;
> +
Similar to my other comment, I would like to see an error path that
unrolls the creation of these on error. It is okay to do this in a
follow-on patch.
Thanks,
Jon
> return 0;
> }
>
>
next prev parent reply other threads:[~2017-05-14 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 14:33 [PATCH V3 0/3] Add/expose control features for the NTB perf test module Gary R Hook
2017-05-09 14:33 ` [PATCH V3 1/3] ntb: Add a module option to control affinity of DMA channels Gary R Hook
2017-05-09 14:33 ` [PATCH V3 2/3] ntb: Remove debug-fs variables from the context structure Gary R Hook
2017-05-14 13:32 ` Jon Mason
2017-05-15 13:48 ` Gary R Hook
2017-05-09 14:33 ` [PATCH V3 3/3] ntb: Add more debugfs support for ntb_perf testing options Gary R Hook
2017-05-14 13:33 ` Jon Mason [this message]
2017-05-09 18:02 ` [PATCH V3 0/3] Add/expose control features for the NTB perf test module Dave Jiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170514133323.GB6027@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Allen.Hubbe@emc.com \
--cc=dave.jiang@intel.com \
--cc=gary.hook@amd.com \
--cc=linux-ntb@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox