Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Elliott, Robert (Servers)" <elliott@hpe.com>,
	Andreas Herrmann <aherrmann@suse.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: [PATCH 1/2] thread_options: Add cgroup_use_bfq
Date: Fri, 28 Aug 2020 17:52:11 -0600	[thread overview]
Message-ID: <031cac45-076a-6e9a-ba5e-2af51ca3f095@kernel.dk> (raw)
In-Reply-To: <DF4PR8401MB10491D443BCBDD8B9586F4FFAB520@DF4PR8401MB1049.NAMPRD84.PROD.OUTLOOK.COM>

On 8/28/20 12:36 PM, Elliott, Robert (Servers) wrote:
> 
> 
>> -----Original Message-----
>> From: fio-owner@vger.kernel.org <fio-owner@vger.kernel.org> On Behalf
>> Of Andreas Herrmann
>> Sent: Friday, August 28, 2020 5:05 AM
>> To: Jens Axboe <axboe@kernel.dk>
>> Cc: fio@vger.kernel.org
>> Subject: [PATCH 1/2] thread_options: Add cgroup_use_bfq
>>
> ...
>> @@ -593,11 +594,13 @@ struct thread_options_pack {
>>  	uint8_t profile[FIO_TOP_STR_MAX];
>>
>>  	/*
>> -	 * blkio cgroup support
>> +	 * (blk)io cgroup support
>>  	 */
>>  	uint8_t cgroup[FIO_TOP_STR_MAX];
>>  	uint32_t cgroup_weight;
>>  	uint32_t cgroup_nodelete;
>> +	uint32_t cgroup_use_bfq;
>> +	uint32_t padding;       /* remove when possible to maintain alignment */
>>
>>  	uint32_t uid;
>>  	uint32_t gid;
> 
> Since the structure already has three pad fields:
>         uint32_t pad;
> 
>         uint64_t size;
> 	...
>         uint32_t pad2;
>         uint64_t rand_seed;
> 	...
>         uint32_t pad3;
>         fio_fp64_t percentile_list[FIO_IO_U_LIST_MAX_LEN];
> 
> pad4 would seem like the natural name for another padding field, and
> the comment doesn't seem necessary.

Also worth checking if you can actually remove padding when updating it,
rather than adding more.

BTW, this is also missing a FIO_SERVER_VER increment, that's needed
whenever thread_options are changed.

-- 
Jens Axboe



  reply	other threads:[~2020-08-28 23:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 10:02 [PATCH 0/2] cgroup: Enable weight tests with cgroup-v2 Andreas Herrmann
2020-08-28 10:04 ` [PATCH 1/2] thread_options: Add cgroup_use_bfq Andreas Herrmann
2020-08-28 18:36   ` Elliott, Robert (Servers)
2020-08-28 23:52     ` Jens Axboe [this message]
2020-08-29  2:14       ` Elliott, Robert (Servers)
2020-08-31  6:07       ` Andreas Herrmann
2020-08-31  6:03     ` Andreas Herrmann
2020-08-28 10:06 ` [PATCH 2/2] cgroup: Allow to use weights with cgroup-v2 Andreas Herrmann

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=031cac45-076a-6e9a-ba5e-2af51ca3f095@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=aherrmann@suse.com \
    --cc=elliott@hpe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox