From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Mike Snitzer <snitzer@redhat.com>, Joe Thornber <ejt@redhat.com>,
<linux-kernel@vger.kernel.org>, <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Ingo Molnar <mingo@kernel.org>, Alasdair Kergon <agk@redhat.com>
Subject: Re: [dm-devel] [RFC][PATCH] dm: Remove dm_bufio_cond_resched()
Date: Fri, 23 Sep 2016 07:32:47 -0700 [thread overview]
Message-ID: <89c9d841-36c4-8b7e-544f-607cbdb2eec0@sandisk.com> (raw)
In-Reply-To: <20160923073435.GL2794@worktop>
On 09/23/16 00:34, Peter Zijlstra wrote:
> Is anybody still using PREEMPT_NONE? Most workloads also care about
> latency to some extend. Lots of code has explicit cond_resched() and
> doesn't worry.
From a SLES11 system:
$ grep PREEMPT_NONE /boot/config-3.0.101-0.47.67-default
CONFIG_PREEMPT_NONE=y
From a SLES12 system:
$ grep CONFIG_PREEMPT_NONE /boot/config-4.4.16-56-default
CONFIG_PREEMPT_NONE=y
Bart.
next prev parent reply other threads:[~2016-09-23 14:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:45 Peter Zijlstra
2016-09-13 12:49 ` Thomas Gleixner
2016-09-13 13:39 ` Mike Snitzer
2016-09-19 10:53 ` Peter Zijlstra
2016-09-22 20:53 ` Mikulas Patocka
2016-09-22 20:59 ` Thomas Gleixner
2016-09-23 7:34 ` Peter Zijlstra
2016-09-23 8:00 ` Thomas Gleixner
2016-09-23 9:05 ` Peter Zijlstra
2016-09-23 9:13 ` Thomas Gleixner
2016-09-23 9:26 ` Ingo Molnar
2016-09-23 12:17 ` Mike Galbraith
2016-09-23 12:26 ` Peter Zijlstra
2016-09-23 12:39 ` Mike Galbraith
2016-09-23 12:42 ` Mike Snitzer
2016-09-23 12:46 ` Peter Zijlstra
2016-09-23 14:32 ` Bart Van Assche [this message]
2016-09-19 9:49 ` Mikulas Patocka
2016-09-19 10:47 ` Peter Zijlstra
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=89c9d841-36c4-8b7e-544f-607cbdb2eec0@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
--cc=snitzer@redhat.com \
--cc=tglx@linutronix.de \
/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®