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: Tue, 5 Jan 2016 20:47:45 +0000 [thread overview]
Message-ID: <20160105204745.760727c1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <568C0DB5.8070200@gmail.com>
> This means that not including the VT subsystem resulted in a 128k
> reduction in runtime footprint, and having only half the number of VT's
> resulted in a 52k reduction. Assuming a linear correlation between the
> number of VT's and the runtime footprint of the subsystem, that means
> the subsystem itself incurs 26k of overhead, and each VT incurs
> approximately 1.6k of overhead.
Doesn't seem an unreasonable value - so yes you've made an argument for
dynamically allocating the vt structures when they are first referenced.
Alan
next prev parent reply other threads:[~2016-01-05 20:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 15:34 [PATCH] Add possibility to set /dev/tty number 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 [this message]
2016-01-06 12:42 ` Austin S. Hemmelgarn
2016-01-06 13:54 ` One Thousand Gnomes
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=20160105204745.760727c1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.