public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: "Z. Majeed" <zmajeed@sbcglobal.net>
To: cygwin-developers@cygwin.com,
	Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: Why is _WIN64 not defined as 1 in _cygwin.h?
Date: Fri, 26 Nov 2021 14:33:54 +0000 (UTC)	[thread overview]
Message-ID: <1907344113.875554.1637937234908@mail.yahoo.com> (raw)
In-Reply-To: <YaC7U69EuSKkcGmU@calimero.vinschen.de>

Good idea! I planned to combine Linux and Windows parts of the failing test to reproduce the inconsistent VmSize issue - but making use of TBB code for a cygwin feature is great - I actually needed RLIMIT_AS for this port too
I looked at fhandler_process.cc last night - adding VmPeak seems just couple lines using Win32 PeakPagefileUsage
 
  On Fri, Nov 26, 2021 at 5:47 AM, Corinna Vinschen<corinna-cygwin@cygwin.com> wrote:   On Nov 25 19:51, Corinna Vinschen wrote:
> On Nov 25 18:06, Z. Majeed wrote:
> > Thanks for clearing that up - I'll send a patch to mingw-w64-public
> > 
> > The porting tip is appreciated - luckily the need for Win32 in the
> > port has been minimal - it may be obviated completely if I can add
> > VmPeak support - and take care of the other issue - a VmSize number
> > that does not match Win32 PagefileUsage
> 
> Yeah, improving Cygwin's /proc/self/status output would be a nice
> option as well, if you'd like to take a stab at it...?

Btw., wouldn't it be great to use your Windows limitMem function as
template to implement getrlimit/setrlimit(RLIMIT_AS) inside Cygwin?


Thanks,
Corinna
  

  reply	other threads:[~2021-11-26 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1016746971.2414349.1637763426878.ref@mail.yahoo.com>
2021-11-24 14:17 ` Z. Majeed
2021-11-25 13:07   ` Corinna Vinschen
2021-11-25 18:06     ` Z. Majeed
2021-11-25 18:51       ` Corinna Vinschen
2021-11-26 10:47         ` Corinna Vinschen
2021-11-26 14:33           ` Z. Majeed [this message]
2021-11-26 16:07             ` Corinna Vinschen
2021-11-27 13:16               ` Z. Majeed
2021-11-29 10:46                 ` Corinna Vinschen
2021-11-29 14:18                   ` Z. Majeed
2021-11-29 14:33                     ` Z. Majeed

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=1907344113.875554.1637937234908@mail.yahoo.com \
    --to=zmajeed@sbcglobal.net \
    --cc=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).