From: Stephen Hemminger <shemminger@osdl.org>
To: george anzinger <george@mvista.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] High-res-timers part 1 (core) take 8
Date: 29 Oct 2002 15:44:08 -0800 [thread overview]
Message-ID: <1035935049.1580.463.camel@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <3DBEE360.EE73EF8C@mvista.com>
Your patch adds a new config option that seems like a step backwards in
ease of use. The CONFIG_TIMERLIST option is adding a new dimension to
complexity kernel configuration. For no other parameter that I can think
of does the kernel configuration process ask for a size information.
Number of users, processes, threads, groups, are all sized dynamically
now; this is good.
How is the end user supposed to know how many timer list entries are
expected? There is no context about what a timer list entry is and no
direct correlation back to anything meaningful in user terms (processes,
devices, sockets, ...). Also, what happens if the time list size is
exhausted? does the kernel die? is it slower?...
Can't this just be dynamically sized?
============================================================================
diff -urP -I \$Id:.*Exp \$ -X /usr/src/patch.exclude
linux-2.5.44-bk1-posix/init/Config.in linux/init/Config.in
--- linux-2.5.44-bk1-posix/init/Config.in Mon Sep 9 10:35:03 2002
+++ linux/init/Config.in Tue Oct 29 07:37:11 2002
@@ -9,6 +9,27 @@
bool 'System V IPC' CONFIG_SYSVIPC
bool 'BSD Process Accounting' CONFIG_BSD_PROCESS_ACCT
bool 'Sysctl support' CONFIG_SYSCTL
+choice 'Size of timer list?' \
+ "512 CONFIG_TIMERLIST_512 \
+ 1024 CONFIG_TIMERLIST_1k \
+ 2048 CONFIG_TIMERLIST_2k \
+ 4096 CONFIG_TIMERLIST_4k \
+ 8192 CONFIG_TIMERLIST_8k" 512
+if [ "$CONFIG_TIMERLIST_512" = "y" ]; then
+ define_int CONFIG_NEW_TIMER_LISTSIZE 512
+fi
+if [ "$CONFIG_TIMERLIST_1k" = "y" ]; then
+ define_int CONFIG_NEW_TIMER_LISTSIZE 1024
+fi
+if [ "$CONFIG_TIMERLIST_2k" = "y" ]; then
+ define_int CONFIG_NEW_TIMER_LISTSIZE 2048
+fi
+if [ "$CONFIG_TIMERLIST_4k" = "y" ]; then
+ define_int CONFIG_NEW_TIMER_LISTSIZE 4096
+fi
+if [ "$CONFIG_TIMERLIST_8k" = "y" ]; then
+ define_int CONFIG_NEW_TIMER_LISTSIZE 8192
+fi
endmenu
next prev parent reply other threads:[~2002-10-29 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 19:37 george anzinger
2002-10-29 23:44 ` Stephen Hemminger [this message]
2002-10-30 7:56 ` george anzinger
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=1035935049.1580.463.camel@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®