git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] check_updates(): effective removal of cache entries marked CE_REMOVE

From
KBKjetil Barvik <barvik@broadpark.no>
Date
Feb 19, 2009, 09:06 UTC
Message-ID
<86ocwy3ido.fsf@broadpark.no>
In-Reply-To
<81b0412b0902190024t3fc7ab20r9a23c72270ac1033@mail.gmail.com>
Alex Riesen <raa.lkml@gmail.com> writes:
Show 25 quoted lines
> 2009/2/18 Kjetil Barvik <barvik@broadpark.no>:
>> If we can trust the numbers from oprofile in this case, we saved
>> approximately ((7710 - 46) * 20000) / (2 * 1000 * 1000 * 1000) = 0.077
>> seconds CPU time with this fix for this particular test.  And notice
>> that now the CPU did only 46 / 15 = 3.1 cycles/instruction.
> ...
>> diff --git a/unpack-trees.c b/unpack-trees.c
>> index e3c3fa1..273b5da 100644
>> --- a/unpack-trees.c
>> +++ b/unpack-trees.c
>> @@ -93,11 +93,9 @@ static int check_updates(struct unpack_trees_options *o)
>>                        display_progress(progress, ++cnt);
>>                        if (o->update)
>>                                unlink_entry(ce);
>> -                       remove_index_entry_at(&o->result, i);
>> -                       i--;
>> -                       continue;
>>                }
>>        }
>> +       remove_marked_cache_entries(&o->result);
>>        remove_scheduled_dirs();
>>
>
> What commit is this change based on? It does not apply to any
> of Junio's master, next, or pu...
  It was based on 'pu', and not a uptodate one.  Sorry about that, I
  will update the patch based on master, and include it together with
  the 2 'USE_NSEC'-patches, which I posted some few days ago.
  -- kjetil
Previous: Alex RiesenNext: Junio C Hamano
Message 4 of 8 in “check_updates(): effective removal of cache entries marked CE_REMOVE”
  1. check_updates(): effective removal of cache entries marked CE_REMOVEKjetil Barvik, Feb 18, 2009
  2. Linus TorvaldsFeb 18, 2009
  3. Alex RiesenFeb 19, 2009
  4. Kjetil BarvikFeb 19, 2009
  5. Junio C HamanoFeb 20, 2009
  6. Kjetil BarvikFeb 20, 2009
  7. Johannes SchindelinFeb 20, 2009
  8. Kjetil BarvikFeb 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.