From: Christoph Hellwig <hch@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs_io: add command line option -M to run as multi threaded process
Date: Sun, 16 Oct 2016 00:16:59 -0700 [thread overview]
Message-ID: <20161016071659.GB17675@infradead.org> (raw)
In-Reply-To: <1476477878-17588-1-git-send-email-amir73il@gmail.com>
On Fri, Oct 14, 2016 at 11:44:38PM +0300, Amir Goldstein wrote:
> xfs_io -M will start by spawning an idle thread.
> The purpose of this idle thread is to test io from a multi threaded
> process. With single threaded process, the file table is not shared
> and file structs are not reference counted.
>
> So in order to detect file struct reference leaks, spawning an idle
> thread will do the trick.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> io/Makefile | 2 +-
> io/init.c | 32 +++++++++++++++++++++++++++++++-
> 2 files changed, 32 insertions(+), 2 deletions(-)
>
> diff --git a/io/Makefile b/io/Makefile
> index 1997ca9..032a8c7 100644
> --- a/io/Makefile
> +++ b/io/Makefile
> @@ -13,7 +13,7 @@ CFILES = init.c \
> mmap.c open.c parent.c pread.c prealloc.c pwrite.c seek.c shutdown.c \
> sync.c truncate.c reflink.c
>
> -LLDLIBS = $(LIBXCMD) $(LIBHANDLE)
> +LLDLIBS = $(LIBXCMD) $(LIBHANDLE) $(LIBPTHREAD)
> LTDEPENDENCIES = $(LIBXCMD) $(LIBHANDLE)
> LLDFLAGS = -static-libtool-libs
>
> diff --git a/io/init.c b/io/init.c
> index 6b88cc6..1d1b97f 100644
> --- a/io/init.c
> +++ b/io/init.c
> @@ -16,6 +16,7 @@
> * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
> */
>
> +#include <pthread.h>
> #include "platform_defs.h"
> #include "command.h"
> #include "input.h"
> @@ -25,6 +26,7 @@
> char *progname;
> int exitcode;
> int expert;
> +int multithreaded;
> size_t pagesize;
> struct timeval stopwatch;
>
> @@ -141,7 +143,7 @@ init(
> pagesize = getpagesize();
> gettimeofday(&stopwatch, NULL);
>
> - while ((c = getopt(argc, argv, "ac:dFfmp:nrRstTVx")) != EOF) {
> + while ((c = getopt(argc, argv, "ac:dFfmMp:nrRstTVx")) != EOF) {
> switch (c) {
> case 'a':
> flags |= IO_APPEND;
> @@ -166,6 +168,9 @@ init(
> exit(1);
> }
> break;
> + case 'M':
> + multithreaded = 1;
> + break;
> case 'n':
> flags |= IO_NONBLOCK;
> break;
> @@ -213,12 +218,37 @@ init(
> add_check_command(init_check_command);
> }
>
> +/*
> + * The purpose of this idle thread is to test io from a multi threaded process.
> + * With single threaded process, the file table is not shared and file structs
> + * are not reference counted. So in order to detect file struct reference
> + * leaks, spawning an idle thread will do the trick.
> + */
> +void *
> +idle_loop(void *arg)
> +{
> + for (;;) pause();
Indentation issue: the pause should on a line of its own.
Otherwise this looks fine to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-10-16 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 20:44 [PATCH] xfs_io: add command line option -M to run as multi threaded process Amir Goldstein
2016-10-16 7:16 ` Christoph Hellwig [this message]
2016-10-16 8:56 ` Amir Goldstein
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=20161016071659.GB17675@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).