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

Re: [PATCH] mem-pool: fix big allocations

From
René Scharfe <l.s.r@web.de>
Date
Dec 24, 2023, 09:30 UTC
Message-ID
<459f63b9-8246-4216-9163-fe69d5ceee83@web.de>
In-Reply-To
<CABPp-BFiK9A6426d7CFeMZvaBcvmShaY9O0krtCe7jeV9wW7nQ@mail.gmail.com>
Am 24.12.23 um 04:11 schrieb Elijah Newren:
Show 5 quoted lines
> On Thu, Dec 21, 2023 at 3:13 PM René Scharfe <l.s.r@web.de> wrote:
>>
>> Add a basic unit test to demonstate the issue by using mem_pool_calloc()
>
> demonstrate (missing 'r')?

Yes. I didn't intend to mention any demons or states, let alone a demon state. *facepalm*

> Nice catch; looks good to me.  Out of curiosity, how'd you find the issue?

I was working on using a memory pool for name-rev. I played with different values for block_alloc, not fully sure why anymore -- either for checking the performance impact or testing robustness.

René
Previous: Elijah NewrenNext: Phillip Wood
Message 3 of 12 in “mem-pool: fix big allocations”
  1. mem-pool: fix big allocationsRené Scharfe, Dec 21, 2023
  2. Elijah NewrenDec 24, 2023
  3. René ScharfeDec 24, 2023
  4. Phillip WoodDec 28, 2023
  5. René ScharfeDec 28, 2023
  6. phillip.wood123@gmail.comDec 28, 2023
  7. René ScharfeDec 28, 2023
  8. phillip.wood123@gmail.comDec 28, 2023
  9. René ScharfeDec 29, 2023
  10. mem-pool: fix big allocationsRené Scharfe, Dec 28, 2023
  11. phillip.wood123@gmail.comDec 28, 2023
  12. Taylor BlauJan 2, 2024

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.