From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mikulas Patocka Subject: Re: [PATCH 0/4] Integrate dm-latency functionality to dm-statistics Date: Wed, 17 Jun 2015 09:22:28 -0400 (EDT) Message-ID: References: <557C6214.4010506@gmail.com> <557EE2C0.2070003@gmail.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: <557EE2C0.2070003@gmail.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: Coly Li Cc: Mike Snitzer , Laurence Oberman , Tao Ma , Robin Dong , dm-devel@redhat.com, "Alasdair G. Kergon" List-Id: dm-devel.ids On Mon, 15 Jun 2015, Coly Li wrote: > >> 2, There should be a maximum latency histogram boundaries limitation. > >> Maybe you do it in the patch and I missed it, that's should be my fault. > > There is no maximum - and there doesn't need to be any maximum because the > > array is allocated dynamically. > Maybe I am too paranoid, IMHO dynamically allocated object should have a > maximum limitation, in case of it occupies too much system resource (e.g > memory here). There is already that limitation of 1/4 total physical memory. Mikulas