From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Pierre Paul MINGOT <mingot.pierre@gmail.com>,
jslaby@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add possibility to set /dev/tty number
Date: Wed, 6 Jan 2016 13:54:39 +0000 [thread overview]
Message-ID: <20160106135439.52231ba2@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <568D0BB6.30606@gmail.com>
> In fact, there already appears to be some degree of allocation on demand
> for VT's (otherwise deallocvt has no point), just not for everything
> associated with the VT. I'd be willing to bet that almost everything
> that reasonably can be dynamically allocated already is, there is a bare
> minimum required for even a virtual device after all.
If there is 1.6K overhead per vt coming from somewhere (given we only
preallocate 1 VT) then either
- There is stuff not being dynamically allocated (which you can find and
fix)
- Your userspace is triggering those dynamic allocations
There is no magic thing that requires 1.6K of kernel data per console.
Alan
next prev parent reply other threads:[~2016-01-06 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 15:34 Pierre Paul MINGOT
2016-01-04 15:43 ` Greg KH
2016-01-04 16:57 ` Austin S. Hemmelgarn
2016-01-04 17:11 ` Greg KH
2016-01-04 18:41 ` Austin S. Hemmelgarn
2016-01-04 22:55 ` One Thousand Gnomes
2016-01-05 13:16 ` Austin S. Hemmelgarn
2016-01-05 15:24 ` Greg KH
2016-01-05 15:33 ` Austin S. Hemmelgarn
2016-01-05 16:11 ` Theodore Ts'o
2016-01-05 16:22 ` Austin S. Hemmelgarn
2016-01-05 8:51 ` Pierre Paul MINGOT
2016-01-05 13:02 ` Austin S. Hemmelgarn
2016-01-05 15:25 ` Greg KH
2016-01-05 15:43 ` Austin S. Hemmelgarn
2016-01-05 16:03 ` Greg KH
2016-01-05 18:38 ` Austin S. Hemmelgarn
2016-01-05 20:47 ` One Thousand Gnomes
2016-01-06 12:42 ` Austin S. Hemmelgarn
2016-01-06 13:54 ` One Thousand Gnomes [this message]
2016-01-06 14:07 ` Austin S. Hemmelgarn
2016-01-06 13:39 ` Austin S. Hemmelgarn
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=20160106135439.52231ba2@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ahferroin7@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingot.pierre@gmail.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
all inboxes | Powered by JetHome®