All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: cang@codeaurora.org, alim.akhtar@samsung.com,
	avri.altman@wdc.com, bvanassche@acm.org,
	Jaegeuk Kim <jaegeuk@google.com>
Subject: [PATCH v3 3/5] scsi: ufs: use WQ_HIGHPRI for gating work
Date: Sat, 24 Oct 2020 08:06:44 -0700	[thread overview]
Message-ID: <20201024150646.1790529-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20201024150646.1790529-1-jaegeuk@kernel.org>

From: Jaegeuk Kim <jaegeuk@google.com>

Must have WQ_MEM_RECLAIM
``WQ_MEM_RECLAIM``
  All wq which might be used in the memory reclaim paths **MUST**
  have this flag set.  The wq is guaranteed to have at least one
  execution context regardless of memory pressure.

Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
---
 drivers/scsi/ufs/ufshcd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index 011e80a21170..bc0d623aed66 100644
--- a/drivers/scsi/ufs/ufshcd.c
+++ b/drivers/scsi/ufs/ufshcd.c
@@ -1867,7 +1867,7 @@ static void ufshcd_init_clk_gating(struct ufs_hba *hba)
 	snprintf(wq_name, ARRAY_SIZE(wq_name), "ufs_clk_gating_%d",
 		 hba->host->host_no);
 	hba->clk_gating.clk_gating_workq = alloc_ordered_workqueue(wq_name,
-							   WQ_MEM_RECLAIM);
+					WQ_MEM_RECLAIM | WQ_HIGHPRI);
 
 	hba->clk_gating.is_enabled = true;
 
-- 
2.29.0.rc1.297.gfa9743e501-goog


WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: avri.altman@wdc.com, cang@codeaurora.org, bvanassche@acm.org,
	alim.akhtar@samsung.com, Jaegeuk Kim <jaegeuk@google.com>
Subject: [f2fs-dev] [PATCH v3 3/5] scsi: ufs: use WQ_HIGHPRI for gating work
Date: Sat, 24 Oct 2020 08:06:44 -0700	[thread overview]
Message-ID: <20201024150646.1790529-4-jaegeuk@kernel.org> (raw)
In-Reply-To: <20201024150646.1790529-1-jaegeuk@kernel.org>

From: Jaegeuk Kim <jaegeuk@google.com>

Must have WQ_MEM_RECLAIM
``WQ_MEM_RECLAIM``
  All wq which might be used in the memory reclaim paths **MUST**
  have this flag set.  The wq is guaranteed to have at least one
  execution context regardless of memory pressure.

Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
---
 drivers/scsi/ufs/ufshcd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index 011e80a21170..bc0d623aed66 100644
--- a/drivers/scsi/ufs/ufshcd.c
+++ b/drivers/scsi/ufs/ufshcd.c
@@ -1867,7 +1867,7 @@ static void ufshcd_init_clk_gating(struct ufs_hba *hba)
 	snprintf(wq_name, ARRAY_SIZE(wq_name), "ufs_clk_gating_%d",
 		 hba->host->host_no);
 	hba->clk_gating.clk_gating_workq = alloc_ordered_workqueue(wq_name,
-							   WQ_MEM_RECLAIM);
+					WQ_MEM_RECLAIM | WQ_HIGHPRI);
 
 	hba->clk_gating.is_enabled = true;
 
-- 
2.29.0.rc1.297.gfa9743e501-goog



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2020-10-24 15:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24 15:06 [UFS v3] UFS fixes Jaegeuk Kim
2020-10-24 15:06 ` [f2fs-dev] " Jaegeuk Kim
2020-10-24 15:06 ` [PATCH v3 1/5] scsi: ufs: atomic update for clkgating_enable Jaegeuk Kim
2020-10-24 15:06   ` [f2fs-dev] " Jaegeuk Kim
2020-10-26  3:28   ` Can Guo
2020-10-26  3:28     ` [f2fs-dev] " Can Guo
2020-10-26  6:13     ` Jaegeuk Kim
2020-10-26  6:13       ` [f2fs-dev] " Jaegeuk Kim
2020-10-26  6:43       ` Can Guo
2020-10-26  6:43         ` [f2fs-dev] " Can Guo
2020-10-26 19:48         ` Jaegeuk Kim
2020-10-26 19:48           ` [f2fs-dev] " Jaegeuk Kim
2020-10-27  2:44           ` Can Guo
2020-10-27  2:44             ` [f2fs-dev] " Can Guo
2020-10-24 15:06 ` [PATCH v3 2/5] scsi: ufs: clear UAC for FFU and RPMB LUNs Jaegeuk Kim
2020-10-24 15:06   ` [f2fs-dev] " Jaegeuk Kim
2020-10-26 18:25   ` asutoshd
2020-10-26 18:25     ` [f2fs-dev] " asutoshd
2020-10-26 19:43     ` Jaegeuk Kim
2020-10-26 19:43       ` [f2fs-dev] " Jaegeuk Kim
2020-10-27 17:48   ` kernel test robot
2020-10-27 17:48     ` kernel test robot
2020-10-24 15:06 ` Jaegeuk Kim [this message]
2020-10-24 15:06   ` [f2fs-dev] [PATCH v3 3/5] scsi: ufs: use WQ_HIGHPRI for gating work Jaegeuk Kim
2020-10-26 18:27   ` asutoshd
2020-10-26 18:27     ` [f2fs-dev] " asutoshd
2020-10-24 15:06 ` [PATCH v3 4/5] scsi: add more contexts in the ufs tracepoints Jaegeuk Kim
2020-10-24 15:06   ` [f2fs-dev] " Jaegeuk Kim
2020-10-24 15:06 ` [PATCH v3 5/5] scsi: ufs: fix clkgating on/off correctly Jaegeuk Kim
2020-10-24 15:06   ` [f2fs-dev] " Jaegeuk Kim
2020-10-26 18:33   ` asutoshd
2020-10-26 18:33     ` [f2fs-dev] " asutoshd

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=20201024150646.1790529-4-jaegeuk@kernel.org \
    --to=jaegeuk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=jaegeuk@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 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.