From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Eric Dumazet" <eric.dumazet@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Neal Cardwell" <ncardwell@google.com>,
"Tom Herbert" <therbert@google.com>,
"Maciej Żenczykowski" <maze@google.com>,
"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
"Ben Hutchings" <bhutchings@solarflare.com>,
"Matt Carlson" <mcarlson@broadcom.com>,
"Michael Chan" <mchan@broadcom.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>
Subject: Re: [PATCH net-next] bnx2x: remove some bloat
Date: Tue, 1 May 2012 09:57:43 +0300 [thread overview]
Message-ID: <1335855463.12363.16.camel@lb-tlvb-eilong.il.broadcom.com> (raw)
In-Reply-To: <1335598761.2900.49.camel@edumazet-glaptop>
On Sat, 2012-04-28 at 09:39 +0200, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Before doing skb->head_frag work on bnx2x driver, I found too much stuff
> was inlined in bnx2x/bnx2x_cmn.h for no good reason and made my work not
> very easy.
>
> Move some big functions out of this include file to the respective .c
> file.
>
> A lot of inline keywords are not needed at all in this huge driver.
>
> text data bss dec hex filename
> 490083 1270 56 491409 77f91 bnx2x/bnx2x.ko.before
> 484206 1270 56 485532 7689c bnx2x/bnx2x.ko
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Eilon Greenstein <eilong@broadcom.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Maciej Żenczykowski <maze@google.com>
> Cc: Neal Cardwell <ncardwell@google.com>
> Cc: Tom Herbert <therbert@google.com>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Cc: Ben Hutchings <bhutchings@solarflare.com>
> Cc: Matt Carlson <mcarlson@broadcom.com>
> Cc: Michael Chan <mchan@broadcom.com>
Acked-by: Eilon Greenstein <eilong@broadcom.com>
Thanks Eric - it makes sense.
prev parent reply other threads:[~2012-05-01 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 7:39 [PATCH net-next] bnx2x: remove some bloat Eric Dumazet
2012-05-01 6:57 ` Eilon Greenstein [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=1335855463.12363.16.camel@lb-tlvb-eilong.il.broadcom.com \
--to=eilong@broadcom.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeffrey.t.kirsher@intel.com \
--cc=maze@google.com \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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