From: Jens Axboe <axboe@kernel.dk>
To: Suresh Dhanarajan <sureshdrajan@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Running fio with offset Increment option
Date: Tue, 17 Apr 2012 08:30:50 +0200 [thread overview]
Message-ID: <4F8D0E1A.2020004@kernel.dk> (raw)
In-Reply-To: <CAN8qX8bNZ4VPFP1a09DdJSaVa2D0MZ0vqLqHF-S4hbdHwuJZcw@mail.gmail.com>
On 04/17/2012 01:15 AM, Suresh Dhanarajan wrote:
> Hi Jens,
>
> I am facing issues while applying the patch,
> Please find the details,
> ===========
> The patch for the file is ,
>
> --- a/fio.h
> +++ b/fio.h
> @@ -67,6 +67,7 @@ struct thread_data {
> char verror[FIO_VERROR_SIZE];
> pthread_t thread;
> unsigned int thread_number;
> + unsigned int group_thread_number;
> unsigned int groupid;
> struct thread_stat ts;
>
> There is no such line in that file.
>
> $>grep 'unsigned int thread_number' fio.h
> extern unsigned int thread_number;
>
> The line 67 does not have any related lines,
>
> 65 enum {
> 66 RW_SEQ_SEQ = 0,
> 67 RW_SEQ_IDENT,
> 68 };
>
> Let me know how to proceed further.
It was against the gfio branch. The line is there in fio.h, it's just
further down and thread_number isn't unsigned :-)
Here's a patch against the master branch, should apply against any
recent version.
diff --git a/filesetup.c b/filesetup.c
index f3d3829..0fc0b41 100644
--- a/filesetup.c
+++ b/filesetup.c
@@ -714,7 +714,7 @@ int setup_files(struct thread_data *td)
need_extend = 0;
for_each_file(td, f, i) {
f->file_offset = td->o.start_offset +
- (td->thread_number - 1) * td->o.offset_increment;
+ (td->group_thread_number - 1) * td->o.offset_increment;
if (!td->o.file_size_low) {
/*
diff --git a/fio.h b/fio.h
index 6da22f0..d4fb907 100644
--- a/fio.h
+++ b/fio.h
@@ -280,6 +280,7 @@ struct thread_data {
char verror[FIO_VERROR_SIZE];
pthread_t thread;
int thread_number;
+ unsigned int group_thread_number;
int groupid;
struct thread_stat ts;
diff --git a/init.c b/init.c
index 3865d09..465ffa9 100644
--- a/init.c
+++ b/init.c
@@ -33,6 +33,7 @@ static int dump_cmdline;
static int def_timeout;
static struct thread_data def_thread;
+static int group_thread_number;
struct thread_data *threads = NULL;
int exitall_on_terminate = 0;
@@ -824,8 +825,10 @@ static int add_job(struct thread_data *td, const char *jobname, int job_add_num)
if ((td->o.stonewall || td->o.new_group) && prev_group_jobs) {
prev_group_jobs = 0;
groupid++;
+ group_thread_number = 0;
}
+ td->group_thread_number = ++group_thread_number;
td->groupid = groupid;
prev_group_jobs++;
--
Jens Axboe
next prev parent reply other threads:[~2012-04-17 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 23:48 Running fio with offset Increment option Suresh Dhanarajan
2012-04-14 15:23 ` Jens Axboe
2012-04-14 15:29 ` Jens Axboe
2012-04-16 23:15 ` Suresh Dhanarajan
2012-04-17 6:30 ` Jens Axboe [this message]
2012-04-18 21:37 ` Suresh Dhanarajan
2012-04-19 5:47 ` Jens Axboe
2012-04-19 19:32 ` Suresh Dhanarajan
2012-04-20 6:27 ` Jens Axboe
2012-04-28 19:09 ` Suresh Dhanarajan
2012-05-02 12:12 ` 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=4F8D0E1A.2020004@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sureshdrajan@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