archive mirror
 help / color / mirror / Atom feed
From: Alex Gaynor <>
To: Fabio Aiuto <>
Cc: rust-for-linux <>
Subject: Re: Question on Box<T> smart pointer
Date: Tue, 27 Apr 2021 11:22:23 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210427152015.GA4653@agape.jhs>

Box<T> in the kernel allocates on the kernel heap, via kmalloc. This
is done by providing a Rust GlobalAllocator:


On Tue, Apr 27, 2021 at 11:20 AM Fabio Aiuto <> wrote:
> Hi all,
> I have a question. There's one thing I miss.
> If Box<T> smart pointer allows allocating space on the heap,
> how is this behaviour overridden in linux kernel Rust?
> I mean, in c we have all API's to allocate heap space,
> but using "pure" Box<T> in kernel space what kind of
> allocation provides?
> If this question is stupid I apologize in advance,
> thank you,
> fabio

All that is necessary for evil to succeed is for good people to do nothing.

  reply	other threads:[~2021-04-27 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 15:20 Question on Box<T> smart pointer Fabio Aiuto
2021-04-27 15:22 ` Alex Gaynor [this message]
2021-04-27 15:33   ` Fabio Aiuto
2021-04-27 15:35     ` Alex Gaynor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).