Re: [PATCH][v2] xfstests: add a option to run xfstests under a cgroup

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On 2/19/20 10:48 AM, Brian Foster wrote:
On Tue, Feb 18, 2020 at 10:27:12AM -0500, Josef Bacik wrote:
I want to add some extended statistic gathering for xfstests, but it's
tricky to isolate xfstests from the rest of the host applications.  The
most straightforward way to do this is to run every test inside of it's
own cgroup.  From there we can monitor the activity of tasks in the
specific cgroup using BPF.

The support for this is pretty simple, allow users to pass -C <cgroup
name>.  We will create the path if it doesn't already exist, and
validate we can add things to cgroup.procs.  If we cannot it'll be
disabled, otherwise we will use this when we do _run_seq by echo'ing the
bash pid into cgroup.procs, which will cause any children to run under
that cgroup.

Signed-off-by: Josef Bacik <josef@xxxxxxxxxxxxxx>
---
v1->v2:
- Changed it from a local.config option to a command line option.
- Export CGROUP2_PATH for everything, utilize that path when generating our
   cgroup for the scripts to run in.

  check          | 24 +++++++++++++++++++++++-
  common/cgroup2 |  2 --
  common/config  |  1 +
  3 files changed, 24 insertions(+), 3 deletions(-)

diff --git a/check b/check
index 2e148e57..df33628e 100755
--- a/check
+++ b/check
@@ -72,6 +72,7 @@ check options
      --large-fs		optimise scratch device for large filesystems
      -s section		run only specified section from config file
      -S section		exclude the specified section from the config file
+    -C cgroup_name	run all the tests in the specified cgroup name
testlist options
      -g group[,group...]	include tests from these groups
@@ -101,6 +102,10 @@ excluded from the list of tests to run from that test dir.
  external_file argument is a path to a single file containing a list of tests
  to exclude in the form of <test dir>/<test name>.
+cgroup_name is just a plain name, or a path relative to the root cgroup path.
+If CGROUP2_PATH does not point at where cgroup2 is mounted then adjust it
+accordingly.
+
  examples:
   check xfs/001
   check -g quick
@@ -307,6 +312,7 @@ while [ $# -gt 0 ]; do
  		;;
  	--large-fs) export LARGE_SCRATCH_DEV=yes ;;
  	--extra-space=*) export SCRATCH_DEV_EMPTY_SPACE=${r#*=} ;;
+	-C)	CGROUP=$2 ; shift ;;
-*) usage ;;
  	*)	# not an argument, we've got tests now.
@@ -509,11 +515,24 @@ _expunge_test()
  OOM_SCORE_ADJ="/proc/self/oom_score_adj"
  test -w ${OOM_SCORE_ADJ} && echo -1000 > ${OOM_SCORE_ADJ}
+# Initialize the cgroup path if it doesn't already exist
+if [ ! -z "$CGROUP" ]; then
+	CGROUP=${CGROUP2_PATH}/${CGROUP}
+	mkdir -p ${CGROUP}
+
+	# If we can't write to cgroup.procs then unset cgroup
+	test -w ${CGROUP}/cgroup.procs || unset CGROUP
+fi
+

Do we need to fix up generic/563 to use this new $CGROUP value, when
set? That test explicitly moves tasks to new/temporary groups, but looks
like it resets back to the top-level CGROUP2_PATH group. I'm not sure
how much that really matters since presumably the next test should move
back into $CGROUP. Otherwise this looks reasonable enough to me.


Wtf I had an explanation for this in my commit message, I must have exited without saving.

I tried to do this actually, and it ended up spewing because you cannot change cgroup.subtree_control for a cgroup you are currently inside of. We can fix this by just making sure all controllers are enabled in our test cgroup, and then fix 562 to not bother messing subtree and just assume everything is enabled. But since it's just one test and I wasn't sure if it would create more wonkiness I just left it as is. I'm open to either solution, I just opted for the less change route. Thanks,

Josef



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux