From: "Michael Chan" <mchan@broadcom.com>
To: "Denys Vlasenko" <vda.linux@googlemail.com>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: bnx2 dirver's firmware images
Date: Tue, 18 Sep 2007 11:45:14 -0700 [thread overview]
Message-ID: <1190141114.9540.216.camel@dell> (raw)
In-Reply-To: <200709181823.26429.vda.linux@googlemail.com>
On Tue, 2007-09-18 at 18:23 +0100, Denys Vlasenko wrote:
> Hi Michael,
>
> In bnx2_fw.h I see the following:
>
> static u32 bnx2_RXP_b06FwBss[(0x13dc/4) + 1] = { 0x0 };
>
> static struct fw_info bnx2_rxp_fw_06 = {
> ...
> .bss = bnx2_RXP_b06FwBss,
> ...
> };
>
> I grepped for the usage of .bss member (grepped for '[.>]bss[^_]')
> and it is used only here:
>
> if (fw->bss) {
> int j;
>
> for (j = 0; j < (fw->bss_len/4); j++, offset += 4) {
> REG_WR_IND(bp, offset, fw->bss[j]);
> }
> }
>
> If I understand it correctly, you read zero words one by one from
> bnx2_RXP_b06FwBss and writing them into the card. This is very
> suboptimal usage of nearly 5k of kernel unswappable memory.
>
> Do you plan to fix it?
We can compress all the different sections of the firmware. Currently,
we only compress the biggest chunks and the rest are uncompressed.
These zeros should compress to almost nothing. But I agree that the
firmware is still big.
>
> Do you have any plans to switch to request_firmware() interface,
> which will allow you to avoid keeping firmware in unswappable kernel
> memory and thus free ~80k?
Matching the correct version of the firmware with the driver is the main
issue.
David, what's your opinion on this?
>
> $ size bnx2.o
> text data bss dec hex filename
> 52255 81551 6360 140166 22386 bnx2.o
> --
> vda
>
next parent reply other threads:[~2007-09-18 17:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709181823.26429.vda.linux@googlemail.com>
2007-09-18 18:45 ` Michael Chan [this message]
2007-09-18 17:55 ` bnx2 dirver's firmware images Denys Vlasenko
2007-09-18 19:09 ` Michael Chan
2007-09-18 18:23 ` David Miller
2007-09-18 18:41 ` H. Peter Anvin
2007-09-18 19:20 ` David Miller
2007-09-18 19:27 ` H. Peter Anvin
2007-09-18 20:08 ` David Miller
2007-09-18 20:35 ` Sam Ravnborg
2007-09-18 20:40 ` H. Peter Anvin
2007-09-19 17:10 ` maximilian attems
2007-09-19 17:12 ` H. Peter Anvin
2007-09-19 17:18 ` maximilian attems
2007-09-19 17:37 ` Sam Ravnborg
2007-09-18 20:05 ` Michael Chan
2007-09-18 19:21 ` David Miller
2007-09-18 21:30 ` Willy Tarreau
2007-09-18 21:31 ` David Miller
2007-09-18 21:37 ` Willy Tarreau
2007-09-18 23:14 ` Michael Chan
2007-09-19 13:40 ` Bill Davidsen
2007-09-19 16:09 ` David Miller
2007-09-19 8:30 ` Denys Vlasenko
2007-09-19 21:00 ` Michael Chan
2007-09-19 20:29 ` Denys Vlasenko
2007-09-19 21:43 ` Michael Chan
2007-09-20 14:49 ` Denys Vlasenko
2007-09-21 2:12 ` Michael Chan
2007-09-19 16:33 ` maximilian attems
2007-09-19 16:38 ` David Miller
2007-09-19 16:51 ` maximilian attems
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=1190141114.9540.216.camel@dell \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vda.linux@googlemail.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).