From: Alex Tomas Subject: Re: ext4-block-reservation.patch Date: Tue, 19 Jun 2007 14:42:02 +0400 Message-ID: <4677B2FA.1060807@clusterfs.com> References: <4677B00A.3010600@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-ext4 To: "Aneesh Kumar K.V" Return-path: Received: from mail.chehov.net ([80.71.245.247]:57679 "EHLO mail.rialcom.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756682AbXFSKmR (ORCPT ); Tue, 19 Jun 2007 06:42:17 -0400 In-Reply-To: <4677B00A.3010600@linux.vnet.ibm.com> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org I considered situation when few CPUs get out of blocks at same time rare. thanks, Alex Aneesh Kumar K.V wrote: > Hi, > > In block reservation code while rebalancing the free blocks why are we > not looking at the reservation slots that have no free blocks left. > Rebalancing > the free blocks equally across all the reservation slots will make sure > we have less chances of failure later when we try to reserve blocks. > > I understand that we consider the CPU slot on which reservation failed > while > rebalancing. But what is preventing considering other CPU slot that > might have > zero blocks left ? > > > > > +void ext4_rebalance_reservation(struct ext4_reservation_slot *rs, __u64 > free) > +{ > + int i, used_slots = 0; > + __u64 chunk; > + > + /* let's know what slots have been used */ > + for (i = 0; i < NR_CPUS; i++) > + if (rs[i].rs_reserved || i == smp_processor_id()) > + used_slots++; > + > + /* chunk is a number of block every used > + * slot will get. make sure it isn't 0 */ > + chunk = free + used_slots - 1; > + do_div(chunk, used_slots); > + > + for (i = 0; i < NR_CPUS; i++) { > + if (free < chunk) > + chunk = free; > + if (rs[i].rs_reserved || i == smp_processor_id()) { > + rs[i].rs_reserved = chunk; > + free -= chunk; > + BUG_ON(free < 0); > + } > + } > + BUG_ON(free); > +} > > > -aneesh > - > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html