Linux PCI Non-Transparent Bridge framework and drivers
 help / color / mirror / Atom feed
From: Gary R Hook <gary.hook@amd.com>
To: linux-ntb@googlegroups.com
Cc: Allen.Hubbe@emc.com, dave.jiang@intel.com, jdmason@kudzu.us
Subject: [PATCH V2 0/3] Add/expose control features for the NTB perf test module
Date: Thu, 4 May 2017 15:21:06 -0500	[thread overview]
Message-ID: <20170504201544.10113.13551.stgit@taos.amd.com> (raw)

The goal of this series is to add and expose some control mechanisms for
the performance test module:
 - Provide a switch to allow memory and threads to be off of the NTB
   node.
 - The debug filesystem entries do not need to be retained after they
   are set up. Remove the variables from the context structure and make
   them automatic, 
 - Create a debug-fs entry for every module parameter. This allows test
   parameters to be changes, and additional tests to be run, without
   unloading ntb_perf the module each time.

---

Gary R Hook (3):
      ntb: Add a module option to control affinity of DMA channels
      ntb: Remove debug-fs variables from the context structure
      ntb: Add more debugfs support for ntb_perf testing options


 drivers/ntb/test/ntb_perf.c |   72 +++++++++++++++++++++++++++++++++----------
 1 file changed, 56 insertions(+), 16 deletions(-)

--
I'm pretty sure donuts would help.

             reply	other threads:[~2017-05-04 20:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 20:21 Gary R Hook [this message]
2017-05-04 20:21 ` [PATCH V2 1/3] ntb: Add a module option to control affinity of DMA channels Gary R Hook
2017-05-04 20:28   ` Dave Jiang
2017-05-04 20:52     ` Gary R Hook
2017-05-04 21:00       ` Gary R Hook
2017-05-04 21:03         ` Dave Jiang
2017-05-04 23:11           ` Gary R Hook
2017-05-04 20:21 ` [PATCH V2 2/3] ntb: Remove debug-fs variables from the context structure Gary R Hook
2017-05-04 20:21 ` [PATCH V2 3/3] ntb: Add more debugfs support for ntb_perf testing options Gary R Hook

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=20170504201544.10113.13551.stgit@taos.amd.com \
    --to=gary.hook@amd.com \
    --cc=Allen.Hubbe@emc.com \
    --cc=dave.jiang@intel.com \
    --cc=jdmason@kudzu.us \
    --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