From: Jens Axboe <axboe@kernel.dk>
To: Roger Sibert <Roger_Sibert@xyratex.com>
Cc: fio@vger.kernel.org
Subject: Re: segfault runninng fio against 2048 jobs
Date: Fri, 20 Apr 2012 08:40:57 +0200 [thread overview]
Message-ID: <4F9104F9.2060308@kernel.dk> (raw)
In-Reply-To: <0FEAAA2D70C89D49A62173478A6C4A5D02DECCD7@XYUS-EX22.xyus.xyratex.com>
On 04/18/2012 09:46 PM, Roger Sibert wrote:
> I verified the patch in fio-2.0.7-11-g7907 and that does indeed look to
> take care of the issue. (Many thanks for that)
>
> Also in follow up I changed the max job limit to 5120 and it seems to
> run properly against that as well.
>
> Question though, is there any reason you have a REAL_MAX_JOBS in fio.h
> and then a FIO_MAX_JOBS in os.h. First glance at it just shows that the
> init.c code uses FIO_MAX_JOBS in for the thread check and then later on
> it uses REAL_MAX_JOBS for the job check except that max_jobs is set
> equal to FIO_MAX_JOBS. It may be that the answer to my question is the
> os-mac.h file which means you have a smaller thread count ... maybe then
> the result is just a small adjustment in the error print to show you
> have exceeded the max # of jobs and or max # of threads.
OSX has a seriously small max segment by default, hence the split and
smaller value there.
I should probably make the thread_data array be segmented, so that fio
could support an arbitrary number of jobs regardless of the max shm
segment size. So far it hasn't been a huge problem.
--
Jens Axboe
next prev parent reply other threads:[~2012-04-20 6:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 21:05 segfault runninng fio against 2048 jobs Roger Sibert
2012-04-18 7:23 ` Jens Axboe
2012-04-18 9:02 ` Roger Sibert
2012-04-18 17:27 ` Roger Sibert
2012-04-18 18:16 ` Roger Sibert
2012-04-18 18:42 ` Jens Axboe
2012-04-18 18:39 ` Jens Axboe
2012-04-18 19:46 ` Roger Sibert
2012-04-20 6:40 ` Jens Axboe [this message]
2012-04-20 14:21 ` Roger Sibert
2012-04-20 14:27 ` Jens Axboe
2012-04-20 16:22 ` Steven Lang
2012-04-20 17:22 ` Jens Axboe
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=4F9104F9.2060308@kernel.dk \
--to=axboe@kernel.dk \
--cc=Roger_Sibert@xyratex.com \
--cc=fio@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 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.