mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "zhaohang (F)" <>
To: "" <>
Cc: "zhangwentao (M)" <>
Subject: [musl] What's the purpose of the __vm_lock?
Date: Thu, 13 Jan 2022 03:09:55 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]


I'm a little confused about the usefulness of __vm_lock. It seems like that __vm_lock was originally cited to prevent the data race condition between pthread_barrier_wait and virtual memory changing, but it can not ensure that the virtual memory of the barrier will not be changed before pthread_barrier_wait. So, what is the meaning that introduce the __vm_lock to prevent the data race?

Thank you.

[-- Attachment #2: Type: text/html, Size: 3050 bytes --]

             reply	other threads:[~2022-01-13  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  3:09 zhaohang (F) [this message]
2022-01-13  3:43 ` Rich Felker

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 \ \ \ \ \
    --subject='Re: [musl] What'\''s the purpose of the __vm_lock?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).