Re: [PATCH] nvme: default to 0 poll queues

2018-12-09 Thread Jens Axboe
On 12/8/18 11:31 PM, Jens Axboe wrote: > On Dec 8, 2018, at 11:22 PM, Guenter Roeck wrote: >> >>> On 12/8/18 9:38 PM, Jens Axboe wrote: On 12/8/18 5:49 PM, Guenter Roeck wrote: Hi, > On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: > We need a better way of config

Re: [PATCH] nvme: default to 0 poll queues

2018-12-08 Thread Guenter Roeck
On 12/8/18 10:31 PM, Jens Axboe wrote: On Dec 8, 2018, at 11:22 PM, Guenter Roeck wrote: On 12/8/18 9:38 PM, Jens Axboe wrote: On 12/8/18 5:49 PM, Guenter Roeck wrote: Hi, On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: We need a better way of configuring this, and given that p

Re: [PATCH] nvme: default to 0 poll queues

2018-12-08 Thread Jens Axboe
On Dec 8, 2018, at 11:22 PM, Guenter Roeck wrote: > >> On 12/8/18 9:38 PM, Jens Axboe wrote: >>> On 12/8/18 5:49 PM, Guenter Roeck wrote: >>> Hi, >>> On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: We need a better way of configuring this, and given that polling is (st

Re: [PATCH] nvme: default to 0 poll queues

2018-12-08 Thread Guenter Roeck
On 12/8/18 9:38 PM, Jens Axboe wrote: On 12/8/18 5:49 PM, Guenter Roeck wrote: Hi, On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: We need a better way of configuring this, and given that polling is (still) a bit niche, let's default to using 0 poll queues. That way we'll have the

Re: [PATCH] nvme: default to 0 poll queues

2018-12-08 Thread Jens Axboe
On 12/8/18 5:49 PM, Guenter Roeck wrote: > Hi, > > On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: >> We need a better way of configuring this, and given that polling is >> (still) a bit niche, let's default to using 0 poll queues. That way >> we'll have the same read/write/poll behavi

Re: [PATCH] nvme: default to 0 poll queues

2018-12-08 Thread Guenter Roeck
Hi, On Mon, Nov 19, 2018 at 08:18:24AM -0700, Jens Axboe wrote: > We need a better way of configuring this, and given that polling is > (still) a bit niche, let's default to using 0 poll queues. That way > we'll have the same read/write/poll behavior as 4.20, and users that > want to test/use poll