public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_UNIX98_PTY_COUNT and devfs
Date: 17 Dec 2003 19:24:27 -0800	[thread overview]
Message-ID: <brr6lb$ev$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.58.0312170131500.397@pervalidus.dyndns.org

Followup to:  <Pine.LNX.4.58.0312170131500.397@pervalidus.dyndns.org>
By author:    =?ISO-8859-1?Q?Fr=E9d=E9ric_L=2E_W=2E_Meunier?= <1@pervalidus.net>
In newsgroup: linux.dev.kernel
>
> I used CONFIG_UNIX98_PTY_COUNT=32 and it created
> /dev/pty/m[0-255]. Is there any way to make devfs only create
> /dev/pty/m[0-31] ?
> 
> From Configure.help:
> 
> "When not in use, each additional set of 256 PTYs occupy
> approximately 8 KB of kernel memory on 32-bit architectures."
> 
> Does that mean it doesn't make any difference if I set
> CONFIG_UNIX98_PTY_COUNT=1 or CONFIG_UNIX98_PTY_COUNT=256, and
> ONFIG_UNIX98_PTY_COUNT=257 will create 512 entries ?
> 

This has absolutely nothing to do with devfs, but Unix98 PTYs
currently come in packs of 256.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

      reply	other threads:[~2003-12-18  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17  3:37 CONFIG_UNIX98_PTY_COUNT and devfs Frédéric L. W. Meunier
2003-12-18  3:24 ` H. Peter Anvin [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='brr6lb$ev$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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