Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] DECstation: Optimised early printk()
Date: Thu, 7 Jun 2007 19:04:04 +0100	[thread overview]
Message-ID: <20070607180404.GA3285@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0706051128210.15653@blysk.ds.pg.gda.pl>

On Tue, Jun 05, 2007 at 11:45:07AM +0100, Maciej W. Rozycki wrote:

>  This is an optimised implementation of early printk() for the DECstation.  
> After the recent conversion to a MIPS-specific generic routine using a 
> character-by-character output the performance dropped significantly.  
> This change reverts to the previous speed -- even at 9600 bps of the 
> serial console the difference is visible with a naked eye; I presume for a 
> framebuffer it is even worse (it may depend on exactly which one is used 
> though).
> 
>  Additionally the change includes a fix for a problem that the old 
> implementation had -- the format used would not actually limit the length 
> of the string output.  This new implementation uses a local buffer to deal 
> with it -- even with this additional copying it is much faster than the 
> generic function.
> 
>  Plus this driver is registered much earlier than the generic one, 
> allowing one to see critical messages, such as one about an incorrect CPU 
> setting used, that are produced beforehand. :-)

Queued up for 2.6.23, too.

>  As a side note, the SYS_HAS_EARLY_PRINTK option could probably be called 
> SYS_HAS_GENERIC_EARLY_PRINTK or something...

I take a patch to rename this :-)

  Ralf

      reply	other threads:[~2007-06-07 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 10:45 [PATCH] DECstation: Optimised early printk() Maciej W. Rozycki
2007-06-07 18:04 ` Ralf Baechle [this message]

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=20070607180404.GA3285@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.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