linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "mannywang(王永峰)" <mannywang@tencent.com>
Cc: hughd <hughd@google.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: Proposal for Creating Shared Memory Areas via a Character Device
Date: Thu, 27 Jun 2024 13:44:09 +0100	[thread overview]
Message-ID: <Zn1emTNZKqDTNyBq@casper.infradead.org> (raw)
In-Reply-To: <tencent_5627BD2E0A6AEFC62A50006B@qq.com>

On Thu, Jun 27, 2024 at 06:53:04PM +0800, mannywang(王永峰) wrote:
> We have identified certain scenarios, such as interactions between
> running Docker containers and their hosts, where there is currently
> no suitable method to efficiently create shared memory areas. This
> limitation arises due to the isolated nature of these environments
> and the assumption that necessary path mappings may not have been
> configured during Docker startup.

What's wrong with shmget()?



      reply	other threads:[~2024-06-27 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 10:53 mannywang(王永峰)
2024-06-27 12:44 ` Matthew Wilcox [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=Zn1emTNZKqDTNyBq@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=mannywang@tencent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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