Comments for "https://os.phil-opp.com/heap-allocation/"

[utterances-bot]

This is a general purpose comment thread for the Heap Allocation post.

[Mubelotix]

Thank you I was waiting this part !

[shakram02]

Hey Philipp, thank you for the great post ( as always ✌️ )

I wanted to note that I think now it's possible to move the allocator to its own module and out of lib.rs because of this PR.

Can't wait for your next tutorial!

[toothbrush7777777]

@phil-opp As @shakram02 noted, rust-lang/rust#62735 now makes it possible to define the global allocator in a submodule.

[phil-opp]

@shakram02 @toothbrush7777777 Thank you for reporting this and sorry for the late reply. I created #714 to move the #[global_allocator] into the allocator module in the post-10 branch and I will create a second pull request to update the blog text in a moment.

Edit: Blog update in #715.

[Menschenkindlein]

The comment in the first code block in https://os.phil-opp.com/heap-allocation/#the-global-allocator-attribute should be // in src/lib.rs.

[phil-opp]

@Menschenkindlein We recently moved the definition to the allocator module in #714. Try updating your Rust nightly if you get an error.

[Menschenkindlein]

I guess it doesn't need allocator:: then, does it?

[phil-opp]

Ah, good catch! Fixed in #728.

[GuillaumeDIDIER]

How do you handle memory allocation failure gracefully in here ? (If my users starts forkbombing I’d like to avoid crashing the kernel and instead tell the user nope, your fork is a spoon)

[phil-opp]

Currently the only way is to use the try_reserve method before appending to collections. I linked the method for Vec, but it also exists for the other collection types. These methods were introduced with the fallible collection allocation 1.0 RFC.

Alternatively, you could create your own alloc library that returns a result instead of panicking for all collection methods. Or, try to get unwinding working with your kernel so that you can catch the oom panic.

[GuillaumeDIDIER]

Going down the rabbit hole in stumbled onto https:/vcombey/fallible_collections not sure if other such crate exist, but this looks like a reasonable thing to use, until hopefully the original alloc crate decides on how to play nice with people who need to handle memory allocation errors. (The ability to have the allocator specify an Error type with the default being ! would imho be very nice)

[phil-opp]

Going down the rabbit hole in stumbled onto https:/vcombey/fallible_collections

Looks useful!

[…] until hopefully the original alloc crate decides on how to play nice with people who need to handle memory allocation errors. (The ability to have the allocator specify an Error type with the default being ! would imho be very nice)

I'm not aware of any proposals to change the global allocator, but there is the allocators working group that works on making collections parametrizable over the separate Alloc trait. The idea is that you can write Vec<T, MyAllocatorType> to make the Vec instance use a different allocator than the global allocator. There was also a discussion on an associated error type: rust-lang/wg-allocators#23.

[n-osborne]

Hello. First, thank you for this amazing tutorial. I really enjoy it.

I do have a build error when using the linked-list-allocator:

error[E0432]: unresolved import `alloc::alloc::AllocRef`

It seems that alloc does not have AllocRef module any more.

[phil-opp]

@n-osborne Thanks! The AllocRef trait was renamed from Alloc recently. Try updating your nightly Rust version to resolve the error.

[n-osborne]

@phil-opp Thanks, it works like a charm.

[imaginezz]

Hi phil-oop, I'm really enjoy your posts, and I have a question: Why alloc method in GlobalAlloc trait returns a mut pointer which type is u8, not usize? I think that data type u8 can not represent a full memory address in the machine.

[bjorn3]

@imaginezz *mut T contains a full memory address for any type T. The choice for u8 as T to form *mut u8 is somewhat arbitrary. It could just as well have been *mut u16 or *mut ().

[toothbrush7777777]

@imaginezz A usize is "The pointer-sized unsigned integer type." *mut u8 is a raw pointer to a u8, not a u8-sized pointer.

[imaginezz]

Yes, it is! *u8 is the pointer to u8 data type like C. Thank you @toothbrush7777777 @bjorn3 very much!

[mitnk]

The tests in tests/heap_allocation.rs can be improved a bit, since all 3 cases are passing for a following broken BumpAllocator implementation:

unsafe impl GlobalAlloc for Locked<BumpAllocator> {
    unsafe fn alloc(&self, layout: Layout) -> *mut u8 {
        self.lock().heap_start as *mut u8
    }

    unsafe fn dealloc(&self, _ptr: *mut u8, _layout: Layout) {
    }
}

Change simple_allocation case like this would catch this issue:

    let heap_value1 = Box::new(41);
    let heap_value2 = Box::new(13);
    assert_eq!(*heap_value1, 41);
    assert_eq!(*heap_value2, 13);

[phil-opp]

@mitnk Good idea! I updated the test as you suggested in b567d06 and 59a7f96.

[dalnefre]

In your previous post you say:

the create_example_mapping function is only a temporary testing function and will be removed after this post, so it is ok. To remind us of the unsafety, we put a FIXME comment on the line.

However, the code still appears in this and future repos. Was this intentional?

[phil-opp]

@dalnefre Sorry, your comment somehow slipped through my notifications. You're completely right, the method should be removed from the code of the subsequent posts. I fixed this in 3a230d0. Thanks for reporting!

[nanoadam]

Thanks for the great tutorials! I am wanting to expand, and was thinking about creating a basic shell (like you announced in edition-3), however kinda confused on how to implement something like that, like how to get a constant stream of key-strokes. Would you have any suggestions?

Or maybe ideas on how to expand on these posts? Challenges? Thanks!

[toothbrush7777777]

Thanks for the great tutorials! I am wanting to expand, and was thinking about creating a basic shell (like you announced in edition-3), however kinda confused on how to implement something like that, like how to get a constant stream of key-strokes. Would you have any suggestions?

You should read https://os.phil-opp.com/async-await/ for an example.
A crate you can use is pc-keyboard.