From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: joe@perches.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 01/14] etherdevice: Add eth_<foo>_addr CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS code
Date: Tue, 03 Mar 2015 14:26:01 -0500 (EST) [thread overview]
Message-ID: <20150303.142601.473683335714577293.davem@davemloft.net> (raw)
In-Reply-To: <1425408125.5130.191.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 03 Mar 2015 10:42:05 -0800
> On Tue, 2015-03-03 at 10:25 -0800, Joe Perches wrote:
>
>> At least for arm gcc 4.6.3, it emits different code
>> for net/l2tp/l2tp_eth.o
>
> Then it looks like arm gcc or arm linux memset() should be improved.
>
> Tracking all memset(x, y, 6) and replace them by some custom version
> seems not very generic to me, when something better can be done.
+1, and none of this stuff is on the fast path anyways.
I think I'll skip this series fornow.
next prev parent reply other threads:[~2015-03-03 19:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 3:54 [PATCH net-next 00/14] Use eth_<foo>_addr instead of memset Joe Perches
2015-03-03 3:54 ` [PATCH net-next 01/14] etherdevice: Add eth_<foo>_addr CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS code Joe Perches
2015-03-03 13:19 ` Eric Dumazet
2015-03-03 18:25 ` Joe Perches
2015-03-03 18:42 ` Eric Dumazet
2015-03-03 19:07 ` Joe Perches
2015-03-03 19:27 ` David Miller
2015-03-03 19:41 ` Joe Perches
2015-03-03 19:56 ` Eric Dumazet
2015-03-03 19:58 ` David Miller
2015-03-03 20:04 ` Joe Perches
2015-03-03 22:01 ` David Miller
2015-03-03 19:26 ` David Miller [this message]
2015-03-03 3:54 ` [PATCH net-next 02/14] ethernet: Use eth_<foo>_addr instead of memset Joe Perches
2015-03-03 4:09 ` Jeff Kirsher
2015-03-05 5:39 ` Don Fry
2015-03-03 3:54 ` [PATCH net-next 03/14] net: usb: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 04/14] wireless: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 05/14] netconsole: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 06/14] xen: " Joe Perches
2015-03-03 10:05 ` Ian Campbell
2015-03-03 10:13 ` Wei Liu
2015-03-03 3:54 ` [PATCH net-next 07/14] 8021q: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 08/14] appletalk: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 09/14] atm: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 10/14] bluetooth: " Joe Perches
2015-03-03 7:04 ` Marcel Holtmann
2015-03-03 3:54 ` [PATCH net-next 11/14] ethernet: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 12/14] mac80211: " Joe Perches
2015-03-03 3:54 ` [PATCH net-next 13/14] wireless: " Joe Perches
2015-03-03 8:16 ` Johannes Berg
2015-03-03 8:37 ` Joe Perches
2015-03-03 8:44 ` Johannes Berg
2015-03-03 8:52 ` Joe Perches
2015-03-03 9:00 ` Johannes Berg
2015-03-03 10:29 ` Joe Perches
2015-03-03 10:34 ` Johannes Berg
2015-03-03 18:57 ` David Miller
2015-03-03 19:03 ` Joe Perches
2015-03-03 19:27 ` David Miller
2015-03-03 19:16 ` Johannes Berg
2015-03-03 3:54 ` [PATCH net-next 14/14] l2tp: " Joe Perches
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=20150303.142601.473683335714577293.davem@davemloft.net \
--to=davem@davemloft.net \
--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
all inboxes | Powered by JetHome®