From: james palmer <james@biobuf.link>
To: 9front@9front.org
Subject: [9front] [PATCH] devproc: use the correct limit when warning that conf.nproc is too high
Date: Mon, 07 Jun 2021 08:39:21 +0000 [thread overview]
Message-ID: <87CC47A3BE3DD1D6C46A7DBCA339BB32@biobuf.link> (raw)
---
diff afe3c1c89a9ead7459691e9bf0d4e28f232bb929 9eb2b302e6240695960f5ce37c68e40a96da44d6
--- a/sys/src/9/port/devproc.c Mon Jun 7 03:17:30 2021
+++ b/sys/src/9/port/devproc.c Mon Jun 7 09:39:21 2021
@@ -281,7 +281,7 @@
static void
procinit(void)
{
- if(conf.nproc >= (1<<(16-QSHIFT))-1)
+ if(conf.nproc >= (1<<23)-1)
print("warning: too many procs for devproc\n");
}
next reply other threads:[~2021-06-09 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:39 james palmer [this message]
2021-06-08 23:59 ` [9front] " Anthony Martin
2021-06-09 2:22 ` ori
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=87CC47A3BE3DD1D6C46A7DBCA339BB32@biobuf.link \
--to=james@biobuf.link \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).