From: Cong Wang <xiyou.wangcong@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Haley <brian.haley@hp.com>
Subject: Re: [PATCH net-next? V2] pktgen: Use simpler test for non-zero ipv6 address
Date: Thu, 11 Oct 2012 10:15:51 +0800 [thread overview]
Message-ID: <CAM_iQpWn8XHZ8VwRGFPjcAvPRAPy82eFT=5tqVzWHq5iXff_wA@mail.gmail.com> (raw)
In-Reply-To: <1349897005.2035.24.camel@joe-AO722>
On Thu, Oct 11, 2012 at 3:23 AM, Joe Perches <joe@perches.com> wrote:
> Reduces object size and should be slightly faster.
>
> allyesconfig:
> $ size net/core/pktgen.o*
> text data bss dec hex filename
> 52284 4321 11840 68445 10b5d net/core/pktgen.o.new
> 52310 4293 11848 68451 10b63 net/core/pktgen.o.old
>
> Signed-off-by: Joe Perches <joe@perches.com>
Looks good.
This should go to -net, net-next is not open currently.
Thanks.
next prev parent reply other threads:[~2012-10-11 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:42 [PATCH net-next?] pktgen: Use simpler test for non-zero ipv6 address Joe Perches
2012-10-10 18:59 ` Brian Haley
2012-10-10 19:01 ` Eric Dumazet
2012-10-10 19:23 ` [PATCH net-next? V2] " Joe Perches
2012-10-10 19:38 ` [RFC net-next] treewide: s/ipv4_is_<foo>()/ipv4_addr_<foo>/ Joe Perches
2012-10-11 0:56 ` [RFC net-next] treewide: s/is_<foo>_ether_addr/eth_addr_<foo> Joe Perches
2012-10-11 8:11 ` [RFC net-next] treewide: s/ipv4_is_<foo>()/ipv4_addr_<foo>/ David Laight
2012-10-11 8:28 ` Joe Perches
2012-10-11 2:15 ` Cong Wang [this message]
2012-10-11 19:20 ` [PATCH net-next? V2] pktgen: Use simpler test for non-zero ipv6 address David Miller
2012-10-11 8:08 ` [PATCH net-next?] " David Laight
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='CAM_iQpWn8XHZ8VwRGFPjcAvPRAPy82eFT=5tqVzWHq5iXff_wA@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=brian.haley@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).