Flexible I/O Tester development
 help / color / mirror / Atom feed
From: vmokric <vojislav.mokric@htec.rs>
To: fio@vger.kernel.org
Subject: FIO blocksize option clear out
Date: Thu, 15 Oct 2015 15:11:36 +0200	[thread overview]
Message-ID: <561FA608.3010904@htec.rs> (raw)
In-Reply-To: <561F97E4.5030807@htec.rs>

Hello members of the fio forum.

In fio man it says that:

blocksize=int[,int], bs=int[,int]
Block size for I/O units. Default: 4k. Values for reads and
writes can be specified separately in the format/read/,/write/,
either of which may be empty to leave that value at its default.

What exactly is blocksize, i.e. block size for I/O units?

I'm rather new in this world of data storages and file systems, I/O
schedulers, block layers, etc., and I'm rather confused with the block
size terminology.

Judging by wiki page on block devices and block sizes: 
http://wiki.linuxquestions.org/wiki/Block_devices_and_block_sizes, what 
FIO impacts over its block size parameter is File system block size, 
right? I saw that people also give another name for file system block 
size: "cluster size".

So, by default block size (File system block size) is 4k. And my
disk physical sector size (disk block size) is also 4k (and there is
another thing: Kernel block size, and I really don't know how this
impacts data transfer to and from my sda disk (with or without caching)
or I have some vague idea...). Let's say that I change my fio block size 
to 1m. My disk block size is still 4k. What is really the difference 
here now, what is changed? Can someone explain or point me to some 
source? I know it's rather newbie question...

And, does IO depth depends on my SATA disk physical characteristics? Can 
I go higher that IO depth = 32 if my disk returns:

root@linaro-gnome:~# hdparm -I /dev/sda | grep Queue
          Queue depth: 32
             *    Native Command Queueing (NCQ)

Thanks,
Vojislav






           reply	other threads:[~2015-10-15 13:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <561F97E4.5030807@htec.rs>]

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=561FA608.3010904@htec.rs \
    --to=vojislav.mokric@htec.rs \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox