How to make fastmap support more cpu cores than 32 or 80

Open
#1 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

Start by reading the freelist and alloc_page_lock logic at the referenced locations in driver/mmap_buffer_hash_table.c, then inspect the related constants in shared_defines.h. Determine what changes are needed for a 256-core configuration and verify that FastMap no longer crashes with that configuration.

Written by the indexing model from the issue text.

Description

I tried to run FastMap on a server with 256 cores, and FastMap crashed at alloc_page_lock. I read the code and found that FastMap only supports 32 and 80 freelists (or cores) according to mmap_buffer_hash_table.c shown below. How to make it variable? I am also confused about setting constants in shared_defines.h? Could you show a correct setting with 256 cores? Thank you.

https://github.com/CARV-ICS-FORTH/FastMap/blob/06a2c9387ce6e8c280d7d01fee02b286e6954ef7/driver/mmap_buffer_hash_table.c#L135

https://github.com/CARV-ICS-FORTH/FastMap/blob/06a2c9387ce6e8c280d7d01fee02b286e6954ef7/driver/mmap_buffer_hash_table.c#L280

Dominant language
C
Stars
37
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CARV-ICS-FORTH/FastMap

All issues in CARV-ICS-FORTH/FastMap

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.