Add option to use spin instead of spinning_top

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
operating-systems

Research direction

Start by reviewing the dependency configuration and the earlier 2020 PR referenced in the issue, then compare how spin and spinning_top are used by linked-list-allocator. Done means the project can select spin without introducing a separate Spinlock type, while preserving the existing allocator use case.

Written by the indexing model from the issue text.

Description

I know this is backtracking on the PR from 2020, but it seems that spin is once again maintained, moreso now than spinning_top.

My project uses spin, as does some of its dependencies (e.g. google/percore). It would be nice if I didn't need to introduce a new Spinlock type into my project just to use linked-list-allocator.

Dominant language
Rust
Stars
242
Forks
56
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 rust-osdev/linked-list-allocator

All issues in rust-osdev/linked-list-allocator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.