linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: "\"J.A. Magallón\"" <jamagallon@ono.com>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Trying to convert old modules to newer kernels
Date: Wed, 26 Dec 2007 19:17:02 -0500	[thread overview]
Message-ID: <4772EEFE.1080503@tmr.com> (raw)
In-Reply-To: <476BACD6.5060900@superbug.co.uk>

James Courtier-Dutton wrote:
> J.A. Magallón wrote:
>>>>>
>>>>> I need to get rid of -mregparm=3 on gcc's command line. It
>>>>> is completely incompatible with the standard calling conventions
>>>>> used in all our assembly-language files in our drivers. We make
>>>>> very high-speed number-crunching drivers that munge high-speed
>>>>> data into images. We need to do that in assembly as we have
>>>>> always done.
>>>>>         
>>
>> Just for curiosity... yep, I understand now you have everything written
>> in assembler, but why not consider start writing it in C and stop
>> doing the compiler work (such as pipelining, out of order reordering,
>> loop unrolling for specific processor, and so on...)
>>
>> That's what everyone taught me, nowadays you won't be better than the
>> compiler in anything longer than three lines...
>>
>>   
> 
> Not true for image processing. compilers are not too good with 
> optimizing mmx and sse algorithms. This is why user space libraries like 
> ffmpeg still use assembly code.

If half of what I read about the Intel compiler is true, that may no 
longer be true.

> That being said, I don't think sse and mmx are available in kernel 
> space, so I would have suggested doing all the grunt work in userspace 
> would be better for this persons application so that he could use sse 
> and mmx etc.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  parent reply	other threads:[~2007-12-26 23:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 20:10 Trying to convert old modules to newer kernels linux-os (Dick Johnson)
2007-12-19 20:23 ` Lennart Sorensen
2007-12-19 20:56   ` linux-os (Dick Johnson)
2007-12-20 15:02     ` Lennart Sorensen
2007-12-20 16:13       ` linux-os (Dick Johnson)
2007-12-20 16:27         ` Lennart Sorensen
2007-12-20 21:23           ` linux-os (Dick Johnson)
2007-12-20 21:40             ` Roland Dreier
2007-12-20 22:56               ` linux-os (Dick Johnson)
2007-12-21 14:39                 ` Lennart Sorensen
2007-12-21 16:37                   ` linux-os (Dick Johnson)
2007-12-29 14:19           ` Jon Masters
2007-12-20 18:28         ` Sam Ravnborg
2007-12-20 21:27           ` linux-os (Dick Johnson)
2007-12-20 22:05             ` Sam Ravnborg
2007-12-20 23:05               ` linux-os (Dick Johnson)
2007-12-20 23:53                 ` J.A. Magallón
2007-12-21 12:08                   ` James Courtier-Dutton
2007-12-21 12:43                     ` Jan Engelhardt
2007-12-27  0:17                     ` Bill Davidsen [this message]
2007-12-21 14:43             ` Lennart Sorensen
2007-12-21 16:39               ` linux-os (Dick Johnson)
2007-12-27  0:19               ` Bill Davidsen
2007-12-19 20:47 ` Jan Engelhardt
2007-12-19 21:10   ` linux-os (Dick Johnson)
2007-12-19 21:16     ` Jan Engelhardt
2007-12-19 20:52 ` Sam Ravnborg
     [not found] <9CdyE-1A6-7@gated-at.bofh.it>
     [not found] ` <9CdIw-1Op-29@gated-at.bofh.it>
     [not found]   ` <9Cebz-2sz-29@gated-at.bofh.it>
     [not found]     ` <9Cvcw-5mu-15@gated-at.bofh.it>
     [not found]       ` <9CwhY-76J-11@gated-at.bofh.it>
     [not found]         ` <9Cyk3-1Zc-29@gated-at.bofh.it>
     [not found]           ` <9CB8a-6zV-13@gated-at.bofh.it>
2007-12-21  0:16             ` Bodo Eggert
2007-12-21 13:11               ` linux-os (Dick Johnson)

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=4772EEFE.1080503@tmr.com \
    --to=davidsen@tmr.com \
    --cc=James@superbug.co.uk \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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;
as well as URLs for NNTP newsgroup(s).