From: "willy tarreau" <wtarreau@yahoo.fr>
To: vda@port.imtp.ilyichevsk.odessa.ua, Bill Davidsen <davidsen@tmr.com>
Cc: Willy TARREAU <willy@w.ods.org>,
willy@meta-x.org, linux-kernel@vger.kernel.org,
Ronald.Wahl@informatik.tu-chemnitz.de
Subject: Re: [ANNOUNCE] CMOV emulation for 2.4.19-rc1
Date: Tue, 2 Jul 2002 08:31:33 +0200 (CEST) [thread overview]
Message-ID: <20020702063133.20857.qmail@web20502.mail.yahoo.com> (raw)
In-Reply-To: <200207020546.g625krT21284@Port.imtp.ilyichevsk.odessa.ua>
> I see a potential problem here: if someone is
> running such kernel all the time, he can take huge
> performance penalty. 'Dunno why but on
> my box mailer does not run. It _crawls_'.
> Ordinary user may perceive it like 'Linux is slow'.
> What can be done to prevent this? Printk can go
> unnoticed in the log, as far as nothing actually
> breaks user won't look into the logs...
As I state in my former mail, I think it would be
good to at least implement statistics on the
number of traps for each instruction set, and
also be able to disable emulation, to check
whether a program correctly runs without
or not.
> 1.big red letters 'CMOV EMULATION' across the
screen? :-)
> 2.Scroll lock LED inverted each time CMOV is
triggered?
> 3.Printk at kernel init time:
> "Emergency rescue kernel with CMOV emulation: can
> be very slow, not for production use!" ?
perhaps not, but we could send an alert message on
the system console the first time an instruction is
emulated, with the program's name. But nothing more,
else we'll have to modify the task struct to include
counters, and I really don't want that.
> Of course (1) is a joke.
so (2) isn't ? and you talk about overhead of 3 IFs
:-)
Cheers,
Willy
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
next prev parent reply other threads:[~2002-07-02 6:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 4:39 Willy TARREAU
2002-07-01 13:58 ` Denis Vlasenko
2002-07-01 13:03 ` willy tarreau
2002-07-01 15:55 ` Bill Davidsen
2002-07-02 10:46 ` Denis Vlasenko
2002-07-02 6:31 ` willy tarreau [this message]
2002-07-02 12:03 ` Denis Vlasenko
2002-07-01 16:25 ` Gabriel Paubert
2002-07-01 17:08 ` willy tarreau
2002-07-01 18:16 ` Denis Vlasenko
2002-07-01 13:25 ` willy tarreau
2002-07-02 20:00 ` Willy TARREAU
2002-07-03 0:36 ` jw schultz
2002-07-18 19:15 ` Robert de Bath
2002-07-18 20:44 ` jw schultz
2002-07-01 18:25 ` Denis Vlasenko
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=20020702063133.20857.qmail@web20502.mail.yahoo.com \
--to=wtarreau@yahoo.fr \
--cc=Ronald.Wahl@informatik.tu-chemnitz.de \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=willy@meta-x.org \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®