From: Greg KH <greg@kroah.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: tapio.laxstrom@iptime.fi, linux-kernel@vger.kernel.org
Subject: Re: drivers/usb/misc/emi*.c have the biggest data objects in the whole tree
Date: Thu, 27 Sep 2007 21:41:11 -0700 [thread overview]
Message-ID: <20070928044111.GB24458@kroah.com> (raw)
In-Reply-To: <200709141135.35239.vda.linux@googlemail.com>
On Fri, Sep 14, 2007 at 11:35:34AM +0100, Denys Vlasenko wrote:
> Hi Tapio,
>
> You are the author of these files. Are you still maintaining them?
> If not, do you know who is the current maintainer?
>
> These two object files hold the biggest data objects in the whole Linux kernel
> after lockdep:
>
> text data bss dec hex filename
> 1258 160516 0 161774 277ee ./drivers/usb/misc/emi26.o
> 1504 209296 0 210800 33770 ./drivers/usb/misc/emi62.o
>
> Basically, these are big arrays of the following structures:
>
> typedef struct _INTEL_HEX_RECORD
> {
> __u32 length;
> __u32 address;
> __u32 type;
> __u8 data[MAX_INTEL_HEX_RECORD_LENGTH];
> } INTEL_HEX_RECORD;
>
> I suggest the following optimizations:
>
> Change structure to
>
> typedef struct _INTEL_HEX_RECORD
> {
> __u8 type;
> __u8 length;
> __u16 address;
> __u8 data[MAX_INTEL_HEX_RECORD_LENGTH];
> } INTEL_HEX_RECORD __attribute__((__packed__));
Only if you redo the whole firmware image too :)
What is this really hurting? It's only relevant if you load the
specific module, if you have this device type. It's a firmware blob,
nothing really interesting at all.
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-28 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 10:35 Denys Vlasenko
2007-09-18 12:21 ` Clemens Ladisch
2007-09-19 2:47 ` Valdis.Kletnieks
2007-09-28 4:41 ` Greg KH [this message]
2007-09-28 11:34 ` Denys Vlasenko
2007-09-28 19:27 ` Greg KH
[not found] ` <200710021018.13905.vda.linux@googlemail.com>
[not found] ` <20071002163532.GA12526@kroah.com>
2007-10-02 17:18 ` testers needed for drivers/usb/misc/emi*.c Denys Vlasenko
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=20070928044111.GB24458@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tapio.laxstrom@iptime.fi \
--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
all inboxes | Powered by JetHome®