From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Li Subject: Re: [PATCH 4/4] mark pseudo users as deleted instead of removing them Date: Fri, 4 Aug 2017 17:14:37 -0400 Message-ID: References: <20170804200915.56738-1-luc.vanoostenryck@gmail.com> <20170804200915.56738-5-luc.vanoostenryck@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-pg0-f45.google.com ([74.125.83.45]:34088 "EHLO mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751312AbdHDVOi (ORCPT ); Fri, 4 Aug 2017 17:14:38 -0400 Received: by mail-pg0-f45.google.com with SMTP id u185so12337407pgb.1 for ; Fri, 04 Aug 2017 14:14:38 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Luc Van Oostenryck Cc: Linux-Sparse On Fri, Aug 4, 2017 at 5:03 PM, Luc Van Oostenryck wrote: >> I am not sure we are on the same page. Only 2 macro need to be updated: >> DO_FOR_EACH_PTR, DO_FOR_EACH_REVERSE. > > It's not for the number of macros defined. > It's about the code size & the run-time effect on the iteration of > the other lists. It seems simple enough but it would add two load-test-branch Because the rm is near the nr, which get visit every loop iteration. >From cache line point of view, the ptrlist->rm will not cause extra cache load. The second test and load will not matter for most of the ptrlist any way. I am willing to bet even my test-ptrlist benchmark will not see much a difference. > to every such macro invocation and these macros are already quite heavy. The flip side is if some one forget to check that, it will be very bad. How do you make sure you add the check to every single one of the loop iterator? I can take patch as it is. It is only a suggestion. No deal breaker. Chris