[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <89c9d841-36c4-8b7e-544f-607cbdb2eec0@sandisk.com>
Date: Fri, 23 Sep 2016 07:32:47 -0700
From: Bart Van Assche <bart.vanassche@...disk.com>
To: Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
CC: Mike Snitzer <snitzer@...hat.com>, Joe Thornber <ejt@...hat.com>,
<linux-kernel@...r.kernel.org>, <dm-devel@...hat.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Alasdair Kergon <agk@...hat.com>
Subject: Re: [dm-devel] [RFC][PATCH] dm: Remove dm_bufio_cond_resched()
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.
Powered by blists - more mailing lists