From: Damien Le Moal <dlemoal@kernel.org>
To: John Garry <john.g.garry@oracle.com>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>,
Nilay Shroff <nilay@linux.ibm.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
nbd@other.debian.org, linux-scsi@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH 05/11] block: add a store_limit operations for sysfs entries
Date: Fri, 10 Jan 2025 18:57:48 +0900 [thread overview]
Message-ID: <d7db7620-1f2e-4216-8929-2cfd4d847447@kernel.org> (raw)
In-Reply-To: <79d85a4e-57c3-454e-a65b-d2a3764eaf0c@oracle.com>
On 2025/01/10 18:56, John Garry wrote:
> On 10/01/2025 05:47, Christoph Hellwig wrote:
>> -static ssize_t queue_iostats_passthrough_store(struct gendisk *disk,
>> - const char *page, size_t count)
>> +static int queue_iostats_passthrough_store(struct gendisk *disk,
>> + const char *page, size_t count, struct queue_limits *lim)
>> {
>> - struct queue_limits lim;
>> unsigned long ios;
>> ssize_t ret;
>>
>> @@ -284,18 +269,13 @@ static ssize_t queue_iostats_passthrough_store(struct gendisk *disk,
>> if (ret < 0)
>> return ret;
>>
>> - lim = queue_limits_start_update(disk->queue);
>> if (ios)
>> - lim.flags |= BLK_FLAG_IOSTATS_PASSTHROUGH;
>> + lim->flags |= BLK_FLAG_IOSTATS_PASSTHROUGH;
>> else
>> - lim.flags &= ~BLK_FLAG_IOSTATS_PASSTHROUGH;
>> -
>> - ret = queue_limits_commit_update(disk->queue, &lim);
>> - if (ret)
>> - return ret;
>> -
>> - return count;
>> + lim->flags &= ~BLK_FLAG_IOSTATS_PASSTHROUGH;
>> + return 0;
>> }
>
> BTW, this function seems to duplicate queue_feature_store(), no?
>
> I mean, why not:
>
> static int queue_iostats_passthrough_store(struct gendisk *disk,
> const char *page, size_t count, struct queue_limits *lim)
> {
> return queue_feature_store(disk, page, count, lim,
> BLK_FLAG_IOSTATS_PASSTHROUGH);
> }
>
> I think that there is even a macro for this.
Another cleanup to add to the pile I guess :)
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-01-10 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 5:47 fix queue freeze and limit locking order v4 Christoph Hellwig
2025-01-10 5:47 ` [PATCH 01/11] block: fix docs for freezing of queue limits updates Christoph Hellwig
2025-01-10 8:43 ` John Garry
2025-01-10 5:47 ` [PATCH 02/11] block: add a queue_limits_commit_update_frozen helper Christoph Hellwig
2025-01-10 5:47 ` [PATCH 03/11] block: check BLK_FEAT_POLL under q_usage_count Christoph Hellwig
2025-01-10 5:47 ` [PATCH 04/11] block: don't update BLK_FEAT_POLL in __blk_mq_update_nr_hw_queues Christoph Hellwig
2025-01-10 5:47 ` [PATCH 05/11] block: add a store_limit operations for sysfs entries Christoph Hellwig
2025-01-10 9:15 ` John Garry
2025-01-10 9:18 ` Christoph Hellwig
2025-01-10 9:51 ` John Garry
2025-01-10 9:56 ` Christoph Hellwig
2025-01-10 9:56 ` John Garry
2025-01-10 9:57 ` Damien Le Moal [this message]
2025-01-10 10:01 ` Christoph Hellwig
2025-01-10 5:47 ` [PATCH 06/11] block: fix queue freeze vs limits lock order in sysfs store methods Christoph Hellwig
2025-01-10 5:47 ` [PATCH 07/11] nvme: fix queue freeze vs limits lock order Christoph Hellwig
2025-01-10 5:47 ` [PATCH 08/11] nbd: " Christoph Hellwig
2025-01-10 5:47 ` [PATCH 09/11] usb-storage: " Christoph Hellwig
2025-01-10 5:47 ` [PATCH 10/11] loop: refactor queue limits updates Christoph Hellwig
2025-01-10 5:47 ` [PATCH 11/11] loop: fix queue freeze vs limits lock order Christoph Hellwig
2025-01-10 14:32 ` fix queue freeze and limit locking order v4 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-01-09 5:57 fix queue freeze and limit locking order v3 Christoph Hellwig
2025-01-09 5:57 ` [PATCH 05/11] block: add a store_limit operations for sysfs entries Christoph Hellwig
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=d7db7620-1f2e-4216-8929-2cfd4d847447@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=nbd@other.debian.org \
--cc=nilay@linux.ibm.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/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.