netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6.24] introduce MAC_FMT/MAC_ARG
Date: Mon, 27 Aug 2007 08:44:17 -0700	[thread overview]
Message-ID: <1188229458.18004.65.camel@localhost> (raw)
In-Reply-To: <1188212049.6756.18.camel@johannes.berg>

On Mon, 2007-08-27 at 12:54 +0200, Johannes Berg wrote:
> Thanks for this patch though, I'd have done it otherwise.

I had it, it was just a s/EUI48/MAC/ and copy/paste thing.

There are also the arch, drivers/[^net], and net directories
that have a few of these.

The patch also added the missing ")" in drivers/net/82596.c

> I was rereading your original conversion and noticed that it is now
> trivial to make the kernel smaller like you originally wanted by doing
> something like this
> 
> -- define this function somewhere --
> print_mac(u8 *mac, char *buf)
> {
> 	sprintf(buf, "%02x:...", mac[0], mac[1], ...);
> }
> EXPORT_SYMBOL(print_mac)
> 
> -- change macros to --
> #define MAC_FMT "%s"
> #define MAC_ARG(a) ({char __buf[18]; print_mac(a, buf); __buf})
> 
> I'm not sure we'd want that, but at the time you said it made the kernel
> significantly smaller and I doubt there's a performance problem with it
> (who prints mac addresses regularly?)

The reduction is ~.1% in an allyesconfig.
The compound statement to hide the automatic works well.
The function call is noise compared to the printk.

cheers, Joe


  reply	other threads:[~2007-08-27 15:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 18:46 [PATCH net-2.6.24] introduce MAC_FMT/MAC_ARG Johannes Berg
2007-08-23 16:01 ` Joe Perches
2007-08-23 16:12   ` Johannes Berg
2007-08-23 17:08     ` John W. Linville
2007-08-25  6:14       ` David Miller
2007-08-26  0:09 ` Joe Perches
2007-08-27 10:54   ` Johannes Berg
2007-08-27 15:44     ` Joe Perches [this message]
2007-08-27 20:41     ` David Miller
     [not found]       ` <1188248263.18004.131.camel@localhost>
2007-08-27 21:09         ` Stephen Hemminger
2007-08-27 21:11         ` David Miller
     [not found]         ` <200708281648.44352.mb@bu3sch.de>
     [not found]           ` <20070828.155419.74563234.davem@davemloft.net>
2007-08-29 17:46             ` Michael Buesch
2007-08-27 21:26       ` Joe Perches
2007-08-27 21:37         ` David Miller
     [not found]           ` <1188335521.6062.56.camel@localhost>
     [not found]             ` <20070828.142216.99461544.davem@davemloft.net>
2007-08-31 22:16               ` Joe Perches
2007-08-31 22:21                 ` Johannes Berg
2007-08-31 22:24                   ` Joe Perches
2007-08-31 22:27                     ` Johannes Berg
2007-08-31 22:32                     ` Johannes Berg
2007-08-31 22:39                       ` Joe Perches
2007-09-14 19:41                 ` Joe Perches
2007-09-14 19:48                   ` David Miller
2007-09-18  2:05                   ` David Miller
2007-09-18  2:14                     ` Joe Perches
2007-09-19  4:50                       ` Joe Perches
2007-09-19 18:11                         ` David Miller
2007-09-19 18:50                           ` Joe Perches
2007-09-19 19:54                             ` David Miller
2007-09-24 17:28                               ` 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=1188229458.18004.65.camel@localhost \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.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;
as well as URLs for NNTP newsgroup(s).