public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda.linux@googlemail.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>,
	James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: mainline aic94xx firmware woes
Date: Mon, 25 Sep 2006 22:49:39 +0200	[thread overview]
Message-ID: <200609252249.39446.vda.linux@googlemail.com> (raw)
In-Reply-To: <20060925101124.GH6374@rhun.haifa.ibm.com>

On Monday 25 September 2006 12:11, Muli Ben-Yehuda wrote:
> Hi,
> 
> The recently merged aic94xx in mainline requires external firmware
> support. This, in turn, necessitates an initrd/initramfs environment
> that includes firmware support to load the firmware. Will a patch to
> optionally include the firmware inline in the kernel and thus not
> having to use an initramfs be acceptable?
> 
> Also, aic94xx does not compile unless FW_LOADER is set in .config due
> to missing 'request_firmware'. What's the right thing to do here -
> aic94xx selecting it, depending on it, or FW_LOADER providing empty
> request_firmware() in case it's compiled out (the last one violates
> the principle of least surprise IMHO).

While we're at it, already existing aicXXXX driver continues to be
insanely large due to excessive inlining of I/O routines:

# x86_64-pc-linux-gnu-size aic7xxx.o
   text    data     bss     dec     hex filename
 118978   22673     568  142219   22b8b aic7xxx.o

This is not even helping performance one iota.
Call overhead for these routines pales in comparison
to I/O instruction stalls, which is in turn pales in comparison to
disk seek delays.

Please do something with it.
--
vda

      parent reply	other threads:[~2006-09-25 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 10:11 mainline aic94xx firmware woes Muli Ben-Yehuda
2006-09-25 10:34 ` Jesper Juhl
2006-09-25 11:30 ` Olaf Hering
2006-09-25 14:07   ` Muli Ben-Yehuda
2006-09-25 11:33 ` Alan Cox
2006-09-25 11:38   ` James Bottomley
2006-09-25 14:10     ` Muli Ben-Yehuda
2006-09-25 20:49 ` Denis Vlasenko [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=200609252249.39446.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=muli@il.ibm.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