From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <Avri.Altman@wdc.com>, Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 0/3] Support disabling fair tag sharing
Date: Thu, 26 Oct 2023 09:37:12 -0700 [thread overview]
Message-ID: <25c8fc74-2583-4e04-8d0e-c65360a1e285@acm.org> (raw)
In-Reply-To: <DM6PR04MB65750819B84D422BD238D2CDFCDEA@DM6PR04MB6575.namprd04.prod.outlook.com>
On 10/25/23 11:50, Avri Altman wrote:
> This issue is known for a long time now.
> Whenever we needed to provide performance measures,
> We used to disable that mechanism, hacking the kernel locally - one way or the other.
> I know that my peers are doing this as well.
The Android 14 kernels have this patch since May (five months ago). None
of the OEMs who use this kernel branch have complained so far.
Thanks,
Bart.
next prev parent reply other threads:[~2023-10-26 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 20:36 [PATCH v4 0/3] Support disabling fair tag sharing Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 1/3] block: Introduce flag BLK_MQ_F_DISABLE_FAIR_TAG_SHARING Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 2/3] scsi: core: Support disabling fair tag sharing Bart Van Assche
2023-10-23 20:36 ` [PATCH v4 3/3] scsi: ufs: Disable " Bart Van Assche
2023-10-24 5:36 ` Avri Altman
2023-10-24 2:28 ` [PATCH v4 0/3] Support disabling " Ming Lei
2023-10-24 16:41 ` Bart Van Assche
2023-10-25 1:33 ` Ming Lei
2023-10-25 18:50 ` Avri Altman
2023-10-26 16:37 ` Bart Van Assche [this message]
2023-10-25 19:01 ` Bart Van Assche
2023-10-25 23:37 ` Ming Lei
2023-10-26 16:29 ` Bart Van Assche
2023-10-31 2:01 ` Yu Kuai
2023-10-31 16:25 ` Bart Van Assche
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=25c8fc74-2583-4e04-8d0e-c65360a1e285@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).