netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Mirosław" <mirqus@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Joe Perches <joe@perches.com>,
	H Hartley Sweeten <hartleys@visionengravers.com>,
	David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] lib/vsprintf.c: Add %pMF to format FDDI bit reversed MAC addresses
Date: Thu, 7 Jan 2010 22:13:18 +0100	[thread overview]
Message-ID: <e2d7436a1001071313r6f5814c9o9d7b2d1c6e162367@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001072037170.13474@eddie.linux-mips.org>

2010/1/7 Maciej W. Rozycki <macro@linux-mips.org>:
> On Thu, 7 Jan 2010, Joe Perches wrote:
>> On Mon, 2010-01-04 at 23:43 +0000, Maciej W. Rozycki wrote:
>> > The example below shows an address, and the sequence of bits or symbols
>> > that would be transmitted when the address is used in the Source Address
>> > or Destination Address fields on the MAC header.  The transmission line
>> > shows the address bits in the order transmitted, from left to right.  For
>> > IEEE 802 LANs these correspond to actual bits on the medium.  The FDDI
>> > symbols line shows how the FDDI PHY sends the address bits as encoded
>> > symbols.
>> >
>> >         MSB:            35:7B:12:00:00:01
>> >         Canonical:      AC-DE-48-00-00-80
>> >         Transmission:   00110101 01111011 00010010 00000000 00000000 00000001
>> >         FDDI Symbols:   35 7B 12 00 00 01"
>> >
>> > Please note that this address has its group bit clear.
>> >
>> >  This notation is also defined in the "FDDI MEDIA ACCESS CONTROL-2
>> > (MAC-2)" (X3T9/92-120) document although that book does not have a need
>> > to use the MSB form and it's skipped.
>>
>> Adds 56 bytes to object size
>>
>> New:
>> $ size lib/vsprintf.o
>>    text          data     bss     dec     hex filename
>>    8714             0       2    8716    220c lib/vsprintf.o
>> old:
>> $ size lib/vsprintf.o
>>    text          data     bss     dec     hex filename
>>    8658             0       2    8660    21d4 lib/vsprintf.o
>
>  What's the gain?  I'd be rather conservative when taking everybody's 56
> bytes for one or two drivers hardly anybody uses.  The format of MAC
> addresses is unlikely to change, so I'd say the sources can live with
> one or two places where the strings are formatted manually.  Even if the
> drivers lose more than these 56 bytes.

Maybe this can be Kconfig-selected by the relevant drivers then?

BTW, the gain is of course consistency and code readability.

Best Regards,
Michał Mirosław

  reply	other threads:[~2010-01-07 21:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BD79186B4FD85F4B8E60E381CAEE19090208954A@mi8nycmail19.Mi8.com>
2010-01-07 18:23 ` [PATCH] lib/vsprintf.c: Add %pMF to format FDDI bit reversed MAC addresses Joe Perches
2010-01-07 20:42   ` Maciej W. Rozycki
2010-01-07 21:13     ` Michał Mirosław [this message]
2010-01-07 22:09     ` David Miller
2010-01-08  0:08       ` Simon Horman
2010-01-08  1:51         ` Joe Perches
2010-01-08  2:48           ` Simon Horman
2010-01-07 21:18   ` Michał Mirosław
2010-01-07 21:36     ` Joe Perches
2010-01-07 21:37     ` [PATCH V2] " Joe Perches
2010-01-07 22:11       ` David Miller
2010-01-07 21:43     ` [PATCH V3] " Joe Perches
2010-01-08  0:58       ` David Miller
2010-01-19 10:57   ` [PATCH] " Andrew Morton

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=e2d7436a1001071313r6f5814c9o9d7b2d1c6e162367@mail.gmail.com \
    --to=mirqus@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hartleys@visionengravers.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.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).