From: Ken Brown <kbrown@cornell.edu>
To: cygwin-devel <cygwin-developers@cygwin.com>
Subject: Shared memory
Date: Thu, 27 Feb 2020 20:35:00 -0000 [thread overview]
Message-ID: <eeef552c-9b61-509b-b918-b8bd01cbe07c@cornell.edu> (raw)
Hi Corinna,
I think I see how to enable FIFOs to be opened for reading multiple times, by
using shared memory to maintain data needed by all readers.
To this end I'm trying to imitate some of what you did in
fhandler_socket_unix.cc, and I find I'm confused about the use of reopen_shmem.
When this is called by fhandler_socket_unix::dup, shouldn't the call actually be
fhs->reopen_shmem () ?
It's the new fhandler that needs to open the shared memory, isn't it? Or am I
misunderstanding something?
Thanks.
Ken
next reply other threads:[~2020-02-27 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 20:35 Ken Brown [this message]
2020-02-28 11:41 ` Corinna Vinschen
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=eeef552c-9b61-509b-b918-b8bd01cbe07c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).