Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 88410 invoked by uid 500); 26 Aug 2001 00:34:10 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 88398 invoked from network); 26 Aug 2001 00:34:10 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Ryan Bloom Reply-To: rbb@covalent.net Organization: Covalent Technologies To: Cliff Woolley , Justin Erenkrantz Subject: Re: SMS parm to bucket_foo_create() Date: Sat, 25 Aug 2001 17:32:58 -0700 X-Mailer: KMail [version 1.2] Cc: References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01082517325809.21862@koj.rkbloom.net> Content-Transfer-Encoding: 8bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Saturday 25 August 2001 17:09, Cliff Woolley wrote: > On Sat, 25 Aug 2001, Justin Erenkrantz wrote: > > > Should the new apr_sms_t* parameter to the foo_create() functions go at > > > the beginning of the argument list or at the end? > > > > I would guess at the end since it is conceptually like a pool. -- justin > > Good, 'cause that's the one I picked. =-) Woah! Those patches were large, and I don't think I agree with them at all. I thoroughly dislike have multiple memory management routines in the same server. Plus, now we sometimes have both pools and sms's in the same structure. How are we synch'ing those two? Why can't we just create a free list for buckets? That way, we take the hit for allocating buckets only when necessary, and at some point, we will reach a steady state. The free list, could be per thread, and I believe I could have it coded tomorrow night. Ryan ______________________________________________________________ Ryan Bloom rbb@apache.org Covalent Technologies rbb@covalent.net --------------------------------------------------------------