Re: [GIT PULL] nvme fixes for 4.20

2018-12-07 Thread Jens Axboe
On 12/7/18 8:38 AM, Christoph Hellwig wrote: > The following changes since commit ba7aeae5539c7a74cf07a2bc61281a93c50e: > > block, bfq: fix decrement of num_active_groups (2018-12-07 07:40:07 -0700) > > are available in the Git repository at: > > git://git.infradead.org/nvme.git

[GIT PULL] nvme fixes for 4.20

2018-12-07 Thread Christoph Hellwig
The following changes since commit ba7aeae5539c7a74cf07a2bc61281a93c50e: block, bfq: fix decrement of num_active_groups (2018-12-07 07:40:07 -0700) are available in the Git repository at: git://git.infradead.org/nvme.git nvme-4.20 for you to fetch changes up to

Re: [GIT PULL] nvme fixes for 4.20

2018-11-30 Thread Jens Axboe
On 11/30/18 9:26 AM, Christoph Hellwig wrote: > On Fri, Nov 30, 2018 at 08:26:24AM -0700, Jens Axboe wrote: >> On 11/30/18 8:24 AM, Christoph Hellwig wrote: >>> Various fixlets all over, including throwing in a 'default y' for the >>> multipath code, given that we want people to actually enable it

Re: [GIT PULL] nvme fixes for 4.20

2018-11-30 Thread Christoph Hellwig
On Fri, Nov 30, 2018 at 08:26:24AM -0700, Jens Axboe wrote: > On 11/30/18 8:24 AM, Christoph Hellwig wrote: > > Various fixlets all over, including throwing in a 'default y' for the > > multipath code, given that we want people to actually enable it for full > > functionality. > > Why enable it

Re: [GIT PULL] nvme fixes for 4.20

2018-11-30 Thread Keith Busch
On Fri, Nov 30, 2018 at 08:26:24AM -0700, Jens Axboe wrote: > On 11/30/18 8:24 AM, Christoph Hellwig wrote: > > Various fixlets all over, including throwing in a 'default y' for the > > multipath code, given that we want people to actually enable it for full > > functionality. > > Why enable it

Re: [GIT PULL] nvme fixes for 4.20

2018-11-30 Thread Jens Axboe
On 11/30/18 8:24 AM, Christoph Hellwig wrote: > Various fixlets all over, including throwing in a 'default y' for the > multipath code, given that we want people to actually enable it for full > functionality. Why enable it by default? 99.9% of users aren't going to care. That seems like an odd

[GIT PULL] nvme fixes for 4.20

2018-11-30 Thread Christoph Hellwig
Various fixlets all over, including throwing in a 'default y' for the multipath code, given that we want people to actually enable it for full functionality. The following changes since commit 14b04063cc994effc86f976625bf8f806d8d44cb: Merge branch 'nvme-4.20' of git://git.infradead.org/nvme

Re: [GIT PULL] nvme fixes for 4.20

2018-11-09 Thread Jens Axboe
On 11/9/18 10:10 AM, Sagi Grimberg wrote: > >>> That is because your for-linus was still 4.20-rc based when >>> I created it. >> >> It's never been 4.20-rc based. After the initial merge, it got based >> on a random commit in the merge window: >> >> commit 3acbd2de6bc3af215c6ed7732dfc097d1e238503

Re: [GIT PULL] nvme fixes for 4.20

2018-11-09 Thread Sagi Grimberg
That is because your for-linus was still 4.20-rc based when I created it. It's never been 4.20-rc based. After the initial merge, it got based on a random commit in the merge window: commit 3acbd2de6bc3af215c6ed7732dfc097d1e238503 Merge: d49f8a52b15b de7d83da84bd Author: Linus Torvalds

Re: [GIT PULL] nvme fixes for 4.20

2018-11-09 Thread Jens Axboe
On 11/9/18 6:20 AM, Christoph Hellwig wrote: > On Fri, Nov 09, 2018 at 06:16:09AM -0700, Jens Axboe wrote: >> On 11/8/18 11:56 PM, Christoph Hellwig wrote: >>> - revert an RDMA commit that didn't help but caused problems >>> - fix another minor P2P fallout >>> - make sure the multipath device

Re: [GIT PULL] nvme fixes for 4.20

2018-11-09 Thread Christoph Hellwig
On Fri, Nov 09, 2018 at 06:16:09AM -0700, Jens Axboe wrote: > On 11/8/18 11:56 PM, Christoph Hellwig wrote: > > - revert an RDMA commit that didn't help but caused problems > > - fix another minor P2P fallout > > - make sure the multipath device inherits the devices limits of > >the

Re: [GIT PULL] nvme fixes for 4.20

2018-11-09 Thread Jens Axboe
On 11/8/18 11:56 PM, Christoph Hellwig wrote: > - revert an RDMA commit that didn't help but caused problems > - fix another minor P2P fallout > - make sure the multipath device inherits the devices limits of >the controllers below > > The following changes since commit

[GIT PULL] nvme fixes for 4.20

2018-11-08 Thread Christoph Hellwig
- revert an RDMA commit that didn't help but caused problems - fix another minor P2P fallout - make sure the multipath device inherits the devices limits of the controllers below The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a: Linux 4.20-rc1 (2018-11-04

Re: [GIT PULL] nvme fixes for 4.20

2018-11-02 Thread Jens Axboe
On 11/2/18 12:37 AM, Christoph Hellwig wrote: > The following changes since commit a5185607787e030fcb0009194d3b12f8bcca59d6: > > block: brd: associate with queue until adding disk (2018-10-31 08:43:09 > -0600) > > are available in the Git repository at: > > git://git.infradead.org/nvme.git

[GIT PULL] nvme fixes for 4.20

2018-11-02 Thread Christoph Hellwig
The following changes since commit a5185607787e030fcb0009194d3b12f8bcca59d6: block: brd: associate with queue until adding disk (2018-10-31 08:43:09 -0600) are available in the Git repository at: git://git.infradead.org/nvme.git nvme-4.20 for you to fetch changes up to