From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Chinner <david@fromorbit.com>, Jian Wen <wenjianhn@gmail.com>
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org, hch@lst.de,
dchinner@redhat.com, Jian Wen <wenjian1@xiaomi.com>,
linux-kernel@vger.kernel.org,
Ankur Arora <ankur.a.arora@oracle.com>
Subject: Re: [PATCH] xfs: explicitly call cond_resched in xfs_itruncate_extents_flags
Date: Fri, 12 Jan 2024 14:01:59 +0100 [thread overview]
Message-ID: <87v87yiu2g.ffs@tglx> (raw)
In-Reply-To: <ZaBPM14r5vGrQ9mc@dread.disaster.area>
On Fri, Jan 12 2024 at 07:27, Dave Chinner wrote:
Cc: Ankur
> On Thu, Jan 11, 2024 at 08:52:22PM +0800, Jian Wen wrote:
>> On Thu, Jan 11, 2024 at 5:38 AM Dave Chinner <david@fromorbit.com> wrote:
>> > IOWs, this is no longer considered an acceptible solution by core
>> > kernel maintainers.
>> Understood. I will only build a hotfix for our production kernel then.
>
> Yeah, that may be your best short term fix. We'll need to clarify
> what the current policy is on adding cond_resched points before we
> go any further in this direction.
Well, right now until the scheduler situation is sorted there is no
other solution than to add the cond_resched() muck.
> Thomas, any update on what is happening with cond_resched() - is
> there an ETA on it going away/being unnecessary?
Ankur is working on that...
next prev parent reply other threads:[~2024-01-12 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:13 [PATCH] xfs: explicitly call cond_resched in xfs_itruncate_extents_flags Jian Wen
2024-01-10 17:45 ` Darrick J. Wong
2024-01-11 12:40 ` Jian Wen
2024-01-11 20:16 ` Dave Chinner
2024-01-10 21:38 ` Dave Chinner
2024-01-11 12:52 ` Jian Wen
2024-01-11 20:27 ` Dave Chinner
2024-01-12 13:01 ` Thomas Gleixner [this message]
2024-01-23 7:01 ` Ankur Arora
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=87v87yiu2g.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ankur.a.arora@oracle.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wenjian1@xiaomi.com \
--cc=wenjianhn@gmail.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 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.