All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	paulmck@linux.vnet.ibm.com,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: 4.2-rc5 rcu stalls.
Date: Wed, 5 Aug 2015 10:46:35 -0400	[thread overview]
Message-ID: <20150805144635.GA5049@codemonkey.org.uk> (raw)
In-Reply-To: <20150805143813.GF7051@lerouge>

On Wed, Aug 05, 2015 at 04:38:14PM +0200, Frederic Weisbecker wrote:
 
 > >  > Also did you just launch trinity? no specific options?
 > >  
 > > basically
 > > 
 > > while [ 1 ];
 > > do
 > >   trinity -N 1000000 -q -l off -C256 -a64 -x fsync -x fdatasync -x syncfs -x sync -P INET --enable-fds=sockets
 > >   sudo ipcrm -a
 > > done
 > > 
 > > (The ipcrm thing is needed for long runs or eventually you oom, because trinity lacks the cleanup smarts)
 > 
 > Ok, can I run that safely on my testbox without it eating some of my files or should
 > I use some special purposed guest?

I wouldn't run it on anything with data I cared about (even nfs mounts)
While there are some safeguards, there might be some cases I've not thought about.

	Dave



  reply	other threads:[~2015-08-05 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 21:08 4.2-rc5 rcu stalls Dave Jones
2015-08-03 21:37 ` Paul E. McKenney
2015-08-03 21:55   ` Dave Jones
2015-08-03 22:03     ` Paul E. McKenney
2015-08-04  4:54       ` Sasha Levin
2015-08-05  0:12         ` Dave Jones
2015-08-05 12:37           ` Frederic Weisbecker
2015-08-05 13:18             ` Dave Jones
2015-08-05 14:38               ` Frederic Weisbecker
2015-08-05 14:46                 ` Dave Jones [this message]
2015-08-06  4:15             ` Dave Jones

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=20150805144635.GA5049@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.