public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Linux usb mailing list <linux-usb-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Something very wrong with time fbcon and FSBR
Date: Sun, 12 Nov 2000 00:54:44 +0100	[thread overview]
Message-ID: <20001112005444.A165@bug.ucw.cz> (raw)

Hi!

I wanted to measure negative impact of FSBR on my system.

I did time cat /etc/termcap. I have fbcon, so it is quite slow
operation. It took 13 seconds.

Then I made system use the FSBR, and did cat /etc/termcap. It was
visually much slower, but it gave 13 seconds again. So I did the same
test again, it said:

0.00user 13.06system 13.38 (0m13.383s) elapsed 97.59%CPU
pavel@bug:~$

but measured with my wristwatch, it took over 50seconds!

Something is very wrong with either USB or fbcon. Okay, now I tried
without USB, it said 

0.00user 12.26system 12.33 (0m12.330s) elapsed 99.44%CPU
pavel@bug:~$

but took 28seconds of real time. So fbcon is making your watch loose
time. Oops. Oh, and fsbr makes system run at roughly half of normal
speed. Not good, either.

								Pavel
PS: fsbr means we make loop in descriptors, which then means uhci
hogging the PCI bus. Would it be possible to do some nop command (send
64 bytes to nonexisting device?) as a part of loop to avoid PCI
overload?
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-11-12 12:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20001112005444.A165@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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