From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: [net-next PATCH 2/2] igb: Make arrays on stack static const to avoid reallocation
Date: Thu, 05 Mar 2015 11:27:15 -0800 [thread overview]
Message-ID: <1425583635.2556.143.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20150305192506.22228.28385.stgit@ahduyck-vm-fedora20>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Thu, 2015-03-05 at 11:25 -0800, Alexander Duyck wrote:
> While addressing the pin problem I noticed that all of the pin
> register
> values where having to be pushed onto the stack each time the function
> was
> called. To avoid that I am making them static const so that they
> should
> only need to be allocated once and we can avoid all the instructions
> to get
> them onto the stack..
>
> size before:
> text data bss dec hex filename
> 161477 10512 8 171997
> 29fdd drivers/net/ethernet/intel/igb/igb.ko
>
> size after:
> text data bss dec hex filename
> 161205 10512 8 171725
> 29ecd drivers/net/ethernet/intel/igb/igb.ko
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@redhat.com>
> ---
> drivers/net/ethernet/intel/igb/igb_ptp.c | 24
> ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
Thanks Alex, I have added your patch to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-05 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 19:24 [net-next PATCH 0/2] Fix some minor issues in igb driver Alexander Duyck
2015-03-05 19:24 ` [net-next PATCH 1/2] igb: Fix warning ‘pin’ may be used uninitialized Alexander Duyck
2015-03-05 19:27 ` Jeff Kirsher
2015-03-05 19:25 ` [net-next PATCH 2/2] igb: Make arrays on stack static const to avoid reallocation Alexander Duyck
2015-03-05 19:27 ` Jeff Kirsher [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=1425583635.2556.143.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@redhat.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
/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