Re: [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
From: Kanchan Joshi <joshi.k@xxxxxxxxxxx>
Date: Mon, 18 Mar 2024 18:56:28 +0530
Cc: linux-block@xxxxxxxxxxxxxxx, Jens Axboe <axboe@xxxxxxxxx>, Ming Lei <ming.lei@xxxxxxxxxx>
Cms-type: 105P
Dlp-filter: Pass
In-reply-to: <e2939a17b63f9347ba3c1c193c4a9306c3ba0845.1710720150.git.asml.silence@gmail.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.1

On 3/18/2024 6:11 AM, Pavel Begunkov wrote:
> uring_cmd implementations should not try to guess issue_flags, use a
> freshly added helper io_uring_cmd_complete() instead.

NVMe interactions look/work fine.

Reviewed-by: Kanchan Joshi <joshi.k@xxxxxxxxxxx>

Follow-Ups:
- Re: [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
  - From: Pavel Begunkov

References:
- [PATCH v2 00/14] remove aux CQE caches
  - From: Pavel Begunkov
- [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
  - From: Pavel Begunkov

Prev by Date: Re: [PATCH] net: Do not break out of sk_stream_wait_memory() with TIF_NOTIFY_SIGNAL
Next by Date: Re: [PATCH v2 05/14] ublk: don't hard code IO_URING_F_UNLOCKED
Previous by thread: [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
Next by thread: Re: [PATCH v2 06/14] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux