DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 4BKBxn5x1383339
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 4BKBxn5x1383339
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=XU22j0aH
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org D780B3858C98
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1734695988;
	bh=ThMIDqGB23ZrvwP4NC+pXR01A134Asc6bJyEtjQyPaM=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=XU22j0aHVzBHgO5v6ap2eeF+z3L3EmQNTtXLyba1qxtyQps7lygsp+1lt2XPMpuUK
	NqG13l2iYcajQgvdAtcyl/XXR/fhSFa++aiHpzzOSo8ueonD7SB6EpSJCOF1ZJ6kIp
	tlnpBRuu4Tbj2kw2Z0qwKqGwyYHDwZvAqrZ0THpw=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 2DB1C3858D20
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 2DB1C3858D20
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1734695923; cv=none;
	b=kPgBmNrtr+PO+F/mlgyoM0U4ejbpUVUWTMC+kb++BYwWO7SQACrFAYlkaky5Np7bfn8OMZ42a/Cu0P72R4tdTD0g20C5bCJCDpghu29Zfso1wHezXNaOIsAdO74Z6kR8fmpYZs+f21faeOHCJn/lmSf3ZdnOLuwWFtDdJwMHwqc=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1734695923; c=relaxed/simple;
	bh=GQuvGATk9K3hDcBrRsDxBC7CETAX/spIfpJY+oIZB00=;
	h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
	b=kU++Xtu9cyRiWmerBfRP76zbA0nXxVxs5IiKCV00wS5Iqq0ttVLOP8vcVs+DuY15dMxuGgZnH6eevxO+CKiQgxJeOb9O/P0eTSwWkFTyQAZ/elSYfLRVQyn1Pj5DABUSdHIvBiDQOZAdOde1dmWjAcFy336gDTOorycsUrXw/Ao=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 2DB1C3858D20
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20230601; t=1734695921; x=1735300721;
	h=to:subject:message-id:date:from:in-reply-to:references:mime-version
	:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
	bh=mFuawdpg2eX9w7pw6tC65bEOzikUiY04qQt5rSD9PlU=;
	b=XEkSzS3UC7antkS/O4DiiWfqfbTZicTzzV4BUVMrUtaeKPM1JGhcb9t94eAgr89WDd
	b8nmzehHz6X7eHDnlTn9j9m8jvQueNTxt+PCR3o0C9xXRF8x4BGMc6xAW9eDwXWeEJX4
	5rdI7/il+beAEPVlSEQTF8UdbWlu0A9BwicLSLO5yUZiJFm5rojqK8Bq0v4jhd7JIqVy
	dbLChS34We2s/2cVeyekv8xkmRpuhDpZ9QGNfDxZ+1ERl3k1O9gjprUknXhIL+cohyq/
	0q6f52cy69xPqPam+rpO+w3hqEPGKirKOBTa5HdWJCDcPe8UECQm3VRCKPCt/XewQRtK
	c8WQ==
X-Gm-Message-State:	AOJu0YwOg2fZkGG1+GAVghHZmTZsRCEwIJK3PSwW/hoI2jXmZO053ttA
	KIn2I37chLTYyuXrq3qz8qWbtBW4WBfiSfmSFJJL1dKicz4EaduJJEnkoKOVjHoS30GbZUE+3OW
	kFpTsRd8FLeDEyfzZygP1qR8BDwoSyIMR
X-Gm-Gg:	ASbGncu05MN3uo3RFnJxKzBTyMO9vxjYdKzQbS9oVMJ0W92AmOoHOtgbrnLgKqKV50e
	xeLlpeblEDmjuW9K5/Q8H38TCjkDcn/q7LQ4Wkg==
X-Google-Smtp-Source:	AGHT+IGNWL9iD0O3VnBSBUg6EduKzq4jm0nTHTdzk8pepBNsy98dGDCWTeEHparY6jnd4rGzswykNWqNiYxhyi0KbPI=
X-Received:	by 2002:a17:906:dc8e:b0:aa6:9e0f:d985 with SMTP id
	a640c23a62f3a-aac2d470b87mr212327366b.35.1734695921463; Fri, 20 Dec 2024
	03:58:41 -0800 (PST)
MIME-Version:	1.0
References:	<CALXu0Uek3sMfifZnOFTCM+ZXJFo2wYEgDBZFZE++Qnq=iB=RBw AT mail DOT gmail DOT com>
	<Z2SvcYR7gFsh7-62 AT calimero DOT vinschen DOT de>
	<6193fecd-9116-4182-82ff-a7bdcc5a6dbd AT SystematicSW DOT ab DOT ca>
In-Reply-To:	<6193fecd-9116-4182-82ff-a7bdcc5a6dbd@SystematicSW.ab.ca>
Date:	Fri, 20 Dec 2024 12:58:05 +0100
Message-ID:	<CALXu0UewYy=q5uzGaG7XP+A5eE1X_u=f0o=Wk=tVZPtY8ShFBw@mail.gmail.com>
Subject:	Re: EPYC 144 core machine has issues with Cygwin PID wraparound
To:	cygwin AT cygwin DOT com
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Cedric Blancher via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Cedric Blancher <cedric DOT blancher AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Fri, 20 Dec 2024 at 01:31, Brian Inglis via Cygwin <cygwin AT cygwin DOT com> wrote:
>
> On 2024-12-19 16:42, Corinna Vinschen via Cygwin wrote:
> > On Dec 19 17:20, Cedric Blancher via Cygwin wrote:
> >> Good afternoon!
> >>
> >> We have a new AMD EPYC machine with 144 cores (upgraded from 8 core
> >> machine) running Windows 10 Enterprise, with a mixture of native Win32
> >> apps+Cygwin.
> >> But the Cygwin apps cause trouble, as PID numbers get re-used too
> >> fast. We churn through ~~6912000 child processes EVERY HOUR, which now
> >> causes major problems with PID wraparounds in scripts and perl.
> >>
> >> 1. How can I increase the value at which pid-wraparound will happen?
> >> 2. How can I test for Cygwins max PID value? Cygwin does not have
> >> /proc/sys/kernel/pid_max
> >
> > We can't make the pid algorithm variable in terms of the max pid, so
> > I changed the maximum PID to the maximum pid on Linux, i.e., 4194304.
> >
> > Please check out the next test release cygwin 3.6.0-0.294.g363357c023ce.
>
> Run the attached to check your upgrade:
>
> $ gcc -o cyg_max_pid{,.c} && ./cyg_max_pid
> max pid 65536
>

Can we please get an interface in /proc OR /bin/getconf to get/probe
the maximum pid value?

Ced
-- 
Cedric Blancher <cedric DOT blancher AT gmail DOT com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -