On Sat, Aug 06, 2022 at 01:22:52PM +0200, Miguel Ojeda wrote: > > I sense possible problems here. It's common for a kernel code to pass > > flags during memory allocations. > > Yes, of course. We will support this, but how exactly it will look > like, to what extent upstream Rust's `alloc` could support our use > cases, etc. has been on discussion for a long time. > > For instance, see https://github.com/Rust-for-Linux/linux/pull/815 for > a potential extension trait approach with no allocator carried on the > type that Andreas wrote after a discussion in the last informal call: > > let a = Box::try_new_atomic(101)?; IMO it's just easier to always pass flags like this: let a = Box::try_new(GFP_KERNEL | GFP_DMA, 101)?; But if allocate_with_flags() will be somehow present in the API that's just what we need. P.S. Thanks for a quick reply!
