From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mikulas Patocka Subject: Re: [PATCH 3/7] dm: add reserved_bio_based_ios module parameter Date: Thu, 12 Sep 2013 19:17:27 -0400 (EDT) Message-ID: References: <1379024698-10487-1-git-send-email-snitzer@redhat.com> <1379024698-10487-4-git-send-email-snitzer@redhat.com> <20130912231135.GC31577@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130912231135.GC31577@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mike Snitzer Cc: dm-devel@redhat.com, Frank Mayhar List-Id: dm-devel.ids On Thu, 12 Sep 2013, Mike Snitzer wrote: > On Thu, Sep 12 2013 at 6:47pm -0400, > Mikulas Patocka wrote: > > > We don't need this. bio-based i/o should be fine with a small mempool, > > there is no need to make it tunable. > > I'd like to get Frank's insight here. He clearly had an interest in > tuning bio-based also. While 16 shouldn't really hurt it could still be > artifically high. I'm not opposed to exposing a sane default but > allowing other to experiemnt (in production workloads) with smaller > values that still enable forward progress should memory get exhausted. > > Mike I would do it this way: if Frank gets a measurable improvement in memory consumption when the values is dropped from 16 to a lower number (4 or maybe 1), then I would drop the value by default (don't make it tunable, drop it for all users). If there is no improvement when the value is lowered, I'd leave it as it is, on 16. Mikulas