linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 202349] Extreme desktop freezes during sustained write operations with XFS
Date: Fri, 25 Jan 2019 09:55:30 +0000	[thread overview]
Message-ID: <bug-202349-201763-w4cTyERu7i@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202349-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202349

Lucas Stach (dev@lynxeye.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dev@lynxeye.de

--- Comment #8 from Lucas Stach (dev@lynxeye.de) ---
So with my GPU developer hat on: What is it that the GPU driver devs should do
to avoid this?
GPU tasks aren't per-se realtime or interactive (think GPU compute tasks with
big working sets, that can take hours or even days to complete). So from the
driver perspective we _want_ FS reclaim to happen instead of failing a task,
but in general for the interactive workload we would rather trash the working
set a bit (by purging clean caches) instead of doing a high latency writeback
of dirty caches.

Also to put the obvious question up again: Why doesn't the reporter see any of
those catastrophic latency events with ext4? It it just that XFS can queue up
way more IO and thus direct reclaim getting stuck behind the already scheduled
IO for a way longer time?

If I understand the problem right, the basic issue is that we still don't have
have IO less dirty throttling in Linux, so we make the interactive GPU process
pay part of the bill of the background process dirtying lots of pages, instead
of throttling this one earlier.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-01-25  9:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 16:50 [Bug 202349] New: Extreme desktop freezes during sustained write operations with XFS bugzilla-daemon
2019-01-19 17:15 ` [Bug 202349] " bugzilla-daemon
2019-01-19 22:20 ` bugzilla-daemon
2019-01-20 21:59 ` bugzilla-daemon
2019-01-21 16:16 ` bugzilla-daemon
2019-01-21 19:04 ` bugzilla-daemon
2019-01-24 11:59 ` bugzilla-daemon
2019-01-24 23:31   ` Dave Chinner
2019-01-24 23:31 ` bugzilla-daemon
2019-01-25  9:55 ` bugzilla-daemon [this message]
2019-01-25 12:50 ` bugzilla-daemon
2019-01-29 22:03 ` bugzilla-daemon
2019-01-30 17:58 ` bugzilla-daemon
2019-01-31 14:56 ` bugzilla-daemon
2019-09-29 11:52 ` bugzilla-daemon
2019-11-22 10:46 ` bugzilla-daemon
2020-03-12 16:12 ` bugzilla-daemon

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=bug-202349-201763-w4cTyERu7i@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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 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).