Re: [dm-devel] dm: Make MIN_IOS, et al, tunable via sysctl.

2013-08-20 Thread Frank Mayhar
On Tue, 2013-08-20 at 17:44 -0400, Mikulas Patocka wrote: > On Mon, 19 Aug 2013, Frank Mayhar wrote: > > On Mon, 2013-08-19 at 10:00 -0400, Mike Snitzer wrote: > > > Performance isn't the concern. The concern is: does DM allow for > > > forward progress if the system's memory is completely exhaust

Re: [dm-devel] dm: Make MIN_IOS, et al, tunable via sysctl.

2013-08-20 Thread Mikulas Patocka
On Mon, 19 Aug 2013, Frank Mayhar wrote: > On Mon, 2013-08-19 at 10:00 -0400, Mike Snitzer wrote: > > Performance isn't the concern. The concern is: does DM allow for > > forward progress if the system's memory is completely exhausted? > > > > This is why request-based has such an extensive re

Re: [dm-devel] dm: Make MIN_IOS, et al, tunable via sysctl.

2013-08-20 Thread Mikulas Patocka
On Mon, 19 Aug 2013, Mike Snitzer wrote: > On Fri, Aug 16 2013 at 6:55pm -0400, > Frank Mayhar wrote: > > > The device mapper and some of its modules allocate memory pools at > > various points when setting up a device. In some cases, these pools are > > fairly large, for example the multipa

Re: [dm-devel] dm: Make MIN_IOS, et al, tunable via sysctl.

2013-08-19 Thread Frank Mayhar
On Mon, 2013-08-19 at 10:00 -0400, Mike Snitzer wrote: > Performance isn't the concern. The concern is: does DM allow for > forward progress if the system's memory is completely exhausted? > > This is why request-based has such an extensive reserve, because it > needs to account for cloning the l