From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>, fio@vger.kernel.org
Subject: Re: Threading vs forking
Date: Mon, 19 Oct 2015 08:40:25 -0600 [thread overview]
Message-ID: <562500D9.2020900@kernel.dk> (raw)
In-Reply-To: <CAF+0mvnWjT5wMpCZzsC6oN_7eobbsqGXdvqdJLxO9M0HFTH9UA@mail.gmail.com>
On 10/10/2015 09:57 PM, Matthew Eaton wrote:
> Hello fio group,
>
> I have been wondering is there any point in telling fio to use threads
> rather than forking on a linux platform? Is there any benefit?
Fio is no different than other programs in that regard. Benefits include
cheaper switching between threads, downsides include things like shared
mm that can hurt you a bit since the threads share the mmap_sem. From
fio's point of view, the option is there so you can choose what best
models the target application.
--
Jens Axboe
prev parent reply other threads:[~2015-10-19 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 3:57 Threading vs forking Matthew Eaton
2015-10-19 14:40 ` Jens Axboe [this message]
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=562500D9.2020900@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=m.eaton82@gmail.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