All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Sandeep Dhavale <dhavale@google.com>
Subject: Re: [PATCH] erofs: use HIPRI by default if per-cpu kthreads are enabled
Date: Tue, 23 May 2023 11:26:29 +0800	[thread overview]
Message-ID: <57c5f06c-ac41-d6c7-3a07-45d07f676577@kernel.org> (raw)
In-Reply-To: <20230522092141.124290-1-hsiangkao@linux.alibaba.com>

On 2023/5/22 17:21, Gao Xiang wrote:
> As Sandeep shown [1], high priority RT per-cpu kthreads are
> typically helpful for Android scenarios to minimize the scheduling
> latencies.
> 
> Switch EROFS_FS_PCPU_KTHREAD_HIPRI on by default if
> EROFS_FS_PCPU_KTHREAD is on since it's the typical use cases for
> EROFS_FS_PCPU_KTHREAD.
> 
> Also clean up unneeded sched_set_normal().
> 
> [1] https://lore.kernel.org/r/CAB=BE-SBtO6vcoyLNA9F-9VaN5R0t3o_Zn+FW8GbO6wyUqFneQ@mail.gmail.com
> Cc: Sandeep Dhavale <dhavale@google.com>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

      parent reply	other threads:[~2023-05-23  3:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  9:21 [PATCH] erofs: use HIPRI by default if per-cpu kthreads are enabled Gao Xiang
2023-05-22  9:21 ` Gao Xiang
2023-05-23  0:52 ` Yue Hu
2023-05-23  0:52   ` Yue Hu
2023-05-23  1:53   ` Gao Xiang
2023-05-23  1:53     ` Gao Xiang
2023-05-23  2:05     ` Yue Hu
2023-05-23  2:05       ` Yue Hu
2023-05-23  2:32 ` Sandeep Dhavale
2023-05-23  2:32   ` Sandeep Dhavale via Linux-erofs
2023-05-23  3:26 ` Chao Yu [this message]

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=57c5f06c-ac41-d6c7-3a07-45d07f676577@kernel.org \
    --to=chao@kernel.org \
    --cc=dhavale@google.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@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.