[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <voitnfv6ipsi4dh4i7hufaq3o3ta2z36paan35yitdwmpl3jvh@2cbmzlv3qlyl>
Date: Tue, 2 Jul 2024 12:45:41 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: yi sun <sunyibuaa@...il.com>
Cc: Tejun Heo <tj@...nel.org>, Yi Sun <yi.sun@...soc.com>,
jiangshanlai@...il.com, jaegeuk@...nel.org, chao@...nel.org, ebiggers@...gle.com,
linux-f2fs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org, niuzhiguo84@...il.com,
Hao_hao.Wang@...soc.com, yunlongxing23@...il.com
Subject: Re: [PATCH v2 1/2] workqueue: new struct io_work
On Tue, Jul 02, 2024 at 05:27:19PM GMT, yi sun wrote:
> Yes, adding the io priority attribute to work will bring huge benefits in the
> following scenarios:
> The system has huge IO pressure (these IOs may all be low-priority IOs),
> and a work (we hope to complete quickly) is also doing IO. If this work
> does not set IO priority, it will be blocked because it is difficult to get IO
> resources. And if this work sets a high IO priority and passes the IO priority
> to kworker, then this work will be completed quickly (as we expect).
Why are you submitting IO from a workqueue in the first place?
Powered by blists - more mailing lists