From: Carlos Llamas <cmllamas@google.com>
To: linux-mm@kvack.org
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Andi Kleen <ak@linux.intel.com>, Hugh Dickins <hughd@google.com>,
Edward Liaw <edliaw@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Header conflicts with shmget() and SHM_HUGE_2MB
Date: Mon, 3 Jun 2024 18:27:23 +0000 [thread overview]
Message-ID: <Zl4LC9lTNptB2xTJ@google.com> (raw)
Hi, I'm trying to figure out how one would use SHM_HUGE_{2MB/1GB}
defines through shmget() from userspace. After having a look at the
man-pages I thought the #include pattern would be similar to that of
mmap(), e.g.:
#include <sys/mman.h>
#include <linux/mman.h>
[...]
mmap(NULL, size, prot, flags | MAP_HUGETLB | MAP_HUGE_2MB,
fd, 0);
However, when doing the shmem equivalent with the headers I get several
redefinition conflicts. When attempting to compile something like this:
#include <sys/shm.h>
#include <linux/shm.h>
[...]
shmid = shmget(key, size, flags | SHM_HUGETLB | SHM_HUGE_2MB);
I run into the following type of issues:
/usr/include/linux/shm.h:26:8: error: redefinition of ‘struct shmid_ds’
26 | struct shmid_ds {
| ^~~~~~~~
In file included from /usr/include/x86_64-linux-gnu/bits/shm.h:45,
from /usr/include/x86_64-linux-gnu/sys/shm.h:30:
/usr/include/x86_64-linux-gnu/bits/types/struct_shmid_ds.h:24:8: note: originally defined here
24 | struct shmid_ds
| ^~~~~~~~
I can see such definitions are tagged as "obsolete" in the uapi headers.
Do we need some ifndef protection with the glibc headers?
What is the advice to follow for userspace? Skip <linux/shm.h> and
openly redefine the SHM_HUGE_* wherever needed?
Thanks,
--
Carlos Llamas
next reply other threads:[~2024-06-03 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:27 Carlos Llamas [this message]
2024-06-03 19:27 ` Header conflicts with shmget() and SHM_HUGE_2MB Andi Kleen
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=Zl4LC9lTNptB2xTJ@google.com \
--to=cmllamas@google.com \
--cc=ak@linux.intel.com \
--cc=edliaw@google.com \
--cc=hughd@google.com \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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;
as well as URLs for NNTP newsgroup(s).