All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: qingwei wei <tchengwee@gmail.com>, fio@vger.kernel.org
Subject: Re: file_service_type and random_distribution
Date: Mon, 16 May 2016 19:20:36 -0600	[thread overview]
Message-ID: <573A71E4.3020404@kernel.dk> (raw)
In-Reply-To: <573A0D4D.8010205@kernel.dk>

On 05/16/2016 12:11 PM, Jens Axboe wrote:
> On 05/16/2016 10:57 AM, Jens Axboe wrote:
>>> I would like to confirm those points is because i intend to run
>>> workload test that simulate hot file access. At any one time, the
>>> files open will be less than the total files in the system and there
>>> will be files that are hot and get access multiple times. Can i do it
>>> using fio? Thanks.
>>
>> That's a good question. Currently fio doesn't, but there's no reason why
>> it could not use the same distribution methods for choosing what files
>> to service. That would indeed allow you to mimic some files being hotter
>> than others, just like we do for offsets in that file.
>
> Something like the below patch would allow you to do that. Basically the
> options and values are idential to random_distribution, this one is just
> for selecting what file to service. Just like with random_distribution,
> you could use fio-genzipf to give you a good idea of what the
> distribution of file uses would be.
>
> Let me know how it works for you.

Committed with some fixes, so you can just use the git version.

-- 
Jens Axboe



  reply	other threads:[~2016-05-17  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  1:59 file_service_type and random_distribution qingwei wei
2016-05-16 16:57 ` Jens Axboe
2016-05-16 18:11   ` Jens Axboe
2016-05-17  1:20     ` Jens Axboe [this message]
2016-05-17  1:25       ` qingwei wei

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=573A71E4.3020404@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=tchengwee@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 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.