mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6: CPU dependent inline in 8250 serial drivers
Date: Wed, 3 Sep 2003 17:05:05 +0100	[thread overview]
Message-ID: <20030903170505.C24951@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030903142758.GA23729@fs.tum.de>; from bunk@fs.tum.de on Wed, Sep 03, 2003 at 04:27:59PM +0200

On Wed, Sep 03, 2003 at 04:27:59PM +0200, Adrian Bunk wrote:
> drivers/serial/8250.h in 2.6 contains the following:
> 
> <--  snip  -->
> 
> ...
> #if defined(__i386__) && (defined(CONFIG_M386) || defined(CONFIG_M486))
> #define SERIAL_INLINE
> #endif
>   
> #ifdef SERIAL_INLINE
> #define _INLINE_ inline
> #else
> #define _INLINE_
> #endif
> ...
> 
> <--  snip  -->
> 
> Why should these functions be inlined only for 386 and 486 CPUs but not 
> for more recent CPUs or other architectures?

The old serial.c did that as well - its mainly there so we don't go
overboard and inline stuff when it isn't necessary.  From what I
remember when this was discussed some time ago, 386 and 486 performs
better when they have the interrupt handling as one function, but
other CPUs perform better when the code is out of line.

Since people tend to care about getting good performance from their
serial ports, I preserved this trick.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-09-03 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 14:27 Adrian Bunk
2003-09-03 16:05 ` Russell King [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=20030903170505.C24951@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.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®