mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, linux-kernel@vger.kernel.org
Subject: Re: speed difference between using hard-linked and modular drives?
Date: Fri, 9 Nov 2001 10:59:21 +1100	[thread overview]
Message-ID: <20011109105921.A6822@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.30.0111081700240.1916-100000@mustard.heime.net> <Pine.LNX.4.33.0111081802380.15975-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0111081802380.15975-100000@localhost.localdomain>

 
> > Are there any speed difference between hard-linked device drivers and
> > their modular counterparts?
> 
> minimal. a few instructions per IO.

Its worse on some architectures that need to pass through a trampoline
when going between kernel and module (eg ppc). Its even worse on ppc64
at the moment because we have a local TOC per module which needs to be
saved and restored.

Anton

  parent reply	other threads:[~2001-11-09  0:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 16:01 Roy Sigurd Karlsbakk
2001-11-08 17:02 ` Ingo Molnar
2001-11-08 17:37   ` Ingo Molnar
2001-11-08 23:59   ` Anton Blanchard [this message]
2001-11-09  5:11     ` Keith Owens
2001-11-10  3:35       ` Anton Blanchard
2001-11-10  7:26         ` Keith Owens
2001-11-08 17:53 ` Robert Love
     [not found] <Pine.LNX.4.33.0111081802380.15975-100000@localhost.localdomain.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.33.0111081836080.15975-100000@localhost.localdomain.suse.lists.linux.kernel>
2001-11-08 23:00   ` Andi Kleen
2001-11-09  0:05     ` Anton Blanchard
2001-11-09  5:45       ` Andi Kleen
2001-11-09  6:04       ` David S. Miller
2001-11-09  6:39         ` Andi Kleen
2001-11-09  6:54           ` Andrew Morton
2001-11-09  7:17           ` David S. Miller
2001-11-09  7:16             ` Andrew Morton
2001-11-09  8:21               ` Ingo Molnar
2001-11-09  7:35                 ` Andrew Morton
2001-11-09  7:44                 ` David S. Miller
2001-11-09  7:24             ` David S. Miller
2001-11-10  4:56           ` Anton Blanchard
2001-11-10  5:09             ` Andi Kleen
2001-11-10 13:44             ` David S. Miller
2001-11-10 13:52             ` David S. Miller
2001-11-10 13:29           ` David S. Miller
2001-11-09  7:14         ` David S. Miller
2001-11-09  7:16         ` David S. Miller
2001-11-09 12:54           ` David S. Miller
2001-11-09 13:15             ` Philip Dodd
2001-11-09 13:17             ` Andi Kleen
2001-11-09 13:25             ` David S. Miller
2001-11-09 13:39               ` Andi Kleen
2001-11-09 13:41               ` David S. Miller
2001-11-09 13:26             ` David S. Miller
2001-11-09 20:45               ` Mike Fedyk
2001-11-09 12:59           ` Alan Cox
2001-11-10  5:20           ` Anton Blanchard
2001-11-09  3:12   ` Rusty Russell
2001-11-09  5:59     ` Andi Kleen
2001-11-09 11:16     ` Helge Hafting
2001-11-12 23:23       ` David S. Miller
2001-11-12 23:14         ` Rusty Russell
2001-11-13  1:30           ` Mike Fedyk
2001-11-13  1:15             ` David Lang
2001-11-12  9:59     ` Rusty Russell

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=20011109105921.A6822@krispykreme \
    --to=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roy@karlsbakk.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

all inboxes | Powered by JetHome®