mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: "Jens Axboe" <axboe@kernel.dk>
Cc: chris.bainbridge@gmail.com, bvanassche@acm.org, hch@lst.de,
	 linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	 regressions@lists.linux.dev, semen.protsenko@linaro.org
Subject: Re: [REGRESSION] ioprio performance hangs, bisected
Date: Sun, 1 Dec 2024 00:59:45 +0800 (CST)	[thread overview]
Message-ID: <3a051f26.3be2.1937e0398a5.Coremail.00107082@163.com> (raw)
In-Reply-To: <09db95ba-b396-4734-9ff0-9331579c92b7@kernel.dk>


At 2024-12-01 00:00:20, "Jens Axboe" <axboe@kernel.dk> wrote:
>On 11/29/24 11:09 PM, David Wang wrote:
>> Would fix/revert reach 6.13-rc1? I think this regression has
>> significant nagative impact on daily usage. From time to time,
>> my system would *stuck* for seconds, sometimes even when
>>  just `cat` some small file it would take seconds, and once,
>> my desktop failed to resume from a suspend, I had to power cycle the system;
>> Polling /proc/diskstats,  I noticed Block-IO read latency,
>> delta(# of milliseconds spent reading)/delta(# of reads completed),
>> is very high, ~200ms average, and frequently reaches 10s.
>>  (Strangely block-io write latency seems normal.)
>> My bisect also land on this commit, revert or apply this patch would
>> fix it.
>> 
>> Kind of think that 6.13-rc1 would be very unpleseant to use without
>> a fix/revert for this.
>
>The pull including this fix has been sent off to Linus yesterday,
>it should make -rc1.
>
>-- 
>Jens Axboe

Good to know~

Thanks
David

      reply	other threads:[~2024-11-30 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 15:44 Chris Bainbridge
2024-11-25 17:16 ` Chris Bainbridge
2024-11-26  6:52   ` Christoph Hellwig
2024-11-26  9:18     ` Chris Bainbridge
2024-11-30  6:09       ` David Wang
2024-11-30 16:00         ` Jens Axboe
2024-11-30 16:59           ` David Wang [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=3a051f26.3be2.1937e0398a5.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=chris.bainbridge@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=semen.protsenko@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®