Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 38199 invoked from network); 12 Jul 2006 00:47:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jul 2006 00:47:59 -0000 Received: (qmail 23920 invoked by uid 500); 12 Jul 2006 00:47:53 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 23873 invoked by uid 500); 12 Jul 2006 00:47:52 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 23862 invoked by uid 99); 12 Jul 2006 00:47:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 17:47:52 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of xiaofeng.li@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 17:47:51 -0700 Received: by ug-out-1314.google.com with SMTP id m3so79428uge for ; Tue, 11 Jul 2006 17:47:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=T9py7t59J4z25/weGOTDrhzoTAYbfoue2u2Q7KaPAXXGZUHAIUKg+5hyYFESfYRSjLE37inVCP90q4vO+dfIvSLKRiUTWXt4NQXfmlk1wGmg67P8xg4CMLhwXxo67lT2MxTcrHNzCLdS+Wi030/Vbqr5TVoQs9WhYSJne3FlL1Q= Received: by 10.67.93.6 with SMTP id v6mr97201ugl; Tue, 11 Jul 2006 17:47:30 -0700 (PDT) Received: by 10.67.32.16 with HTTP; Tue, 11 Jul 2006 17:47:30 -0700 (PDT) Message-ID: <9623c9a50607111747y78be3926sb94b5568e297c07@mail.gmail.com> Date: Wed, 12 Jul 2006 08:47:30 +0800 From: "Xiao-Feng Li" To: harmony-dev@incubator.apache.org, geir@pobox.com Subject: Re: [DRLVM] GC/VM interface discussion In-Reply-To: <44B3E2F2.3070102@pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4dd1f3f00607080911r7522156fv9cc11c36b0e23f7c@mail.gmail.com> <9623c9a50607100203u2605755fma3cc620f6e2ba617@mail.gmail.com> <12385bbd0607100559p54c12c90g8584b3293d2dac53@mail.gmail.com> <9623c9a50607110105u531225b2ma6792e62b6a13b45@mail.gmail.com> <12385bbd0607110518r75e9da2v5e8c5b25debadda3@mail.gmail.com> <44B3BB0F.4090706@Intel.com> <44B3E2F2.3070102@pobox.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/12/06, Geir Magnusson Jr wrote: > > > > 1) gc_pin() is optional operation, and may be absent in simplest collectors > > 2) gc_pin() is not required to succeed, and the GC may decide to reject > > object pinning (e.g. based on some memory footprint/performance compromise). > > The success of operation must be checked by using gc_is_object_pinned() > > Do you mean gc_pin_object()? It returns void. Why not have it return > an indication of success? I mean, it knows, right? > My understanding is, as a hint to GC, gc_pin_object() leaves GC to decide when and how to react; so the immediate return value may not be very informative to indicate the status of an object pinning, since GC may pin it later in next collection, the API itself doesn't need to know the result. The gc_is_object_pinned is used to check the pinning status. That said, it's still ok to return the current pinning status at the return time. Thanks, xiaofeng --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org