From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: Size of fhandler_fifo
Date: Mon, 9 Nov 2020 10:15:29 +0100 [thread overview]
Message-ID: <20201109091529.GW33165@calimero.vinschen.de> (raw)
In-Reply-To: <8814992e-ef08-31f5-3086-ad1caafff4de@cornell.edu>
On Nov 7 10:19, Ken Brown via Cygwin-developers wrote:
> Hi Corinna,
>
> This is a followup to your question on IRC about why fhandler_fifo is so
> big. The main reason is the pipe_name_buf member, which occupies 96 bytes
> and stores the Windows named pipe name.
>
> There's a similar need to store the pipe name for the fhandler_socket_unix
> class. In that case you used pc.{set,get}_nt_native_path. But the latter
> is already in use in the fhandler_fifo case, so I can't use that. I see
> several possible ways to proceed:
>
> 0. Do nothing and live with fhandler_fifo being big (736 bytes on 64-bit).
As I wrote on IRC, it's not that bad. Trying to keep the size of
fhandlers low is probably a bit old-fashioned anyway. 32 bit trauma :)
Corinna
prev parent reply other threads:[~2020-11-09 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 15:19 Ken Brown
2020-11-08 13:11 ` Ken Brown
2020-11-09 9:15 ` Corinna Vinschen [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=20201109091529.GW33165@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).