From: Mike Galbraith <efault@gmx.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: NFS: 82ms wakeup latency 4.14-rc4
Date: Mon, 18 Dec 2017 17:48:06 +0100 [thread overview]
Message-ID: <1513615686.7113.10.camel@gmx.de> (raw)
In-Reply-To: <20171218163559.GA11829@fieldses.org>
On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote:
>
> This probably just shows I don't understand the issues, but: isn't this
> the job of preemption?
If this were a PREEMPT kernel, yes, we'd check need_resched() on lock
release etc, but it's a PREEMPT_VOLUNTARY kernel.
-Mike
next prev parent reply other threads:[~2017-12-18 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:17 NFS: 82ms wakeup latency 4.14-rc4 Mike Galbraith
2017-12-18 15:31 ` Mike Galbraith
2017-12-18 16:35 ` J. Bruce Fields
2017-12-18 16:48 ` Mike Galbraith [this message]
2017-12-18 17:00 ` Mike Galbraith
2017-12-18 17:17 ` Mike Galbraith
2017-12-18 17:27 ` J. Bruce Fields
2017-12-18 17:47 ` Mike Galbraith
2017-12-18 18:34 ` Mike Galbraith
2017-12-18 17:24 ` Trond Myklebust
2017-12-18 17:24 ` Trond Myklebust
2017-12-18 17:26 ` Mike Galbraith
2018-01-02 20:29 ` [patch] fs/nfs: Add a resched point to nfs_commit_release_pages() Mike Galbraith
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=1513615686.7113.10.camel@gmx.de \
--to=efault@gmx.de \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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.