netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Dillow <dave@thedillows.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Ingo Oeser <netdev@axxeo.de>, Denis Vlasenko <vda@ilport.com.ua>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [RFD][PATCH] typhoon and core sample for folding away VLAN stuff
Date: Wed, 12 Apr 2006 21:24:00 -0400	[thread overview]
Message-ID: <443DA830.8030209@thedillows.org> (raw)
In-Reply-To: <200604122132.46113.ioe-lkml@rameria.de>

Ingo Oeser wrote:
> Dave Dillow: Is this style clean enough to have it in your driver?

Though I'm not real fond of Denis's last patch, I think I prefer it's 
style to this, solely because it removes more code when VLANs are 
disabled -- you've left the spin_locks in, and have more #ifdefs.

Regardless, I remain opposed to this particular instance of bloat 
busting. While both patches have improved in style, they remove a useful 
feature and make the code less clean, for no net gain.

> This kind of changes are important, because bloat creeps in byte by byte
> of unused features. So I really appreciate your work here Denis.

On SMP FC4, typhoon.ko has a text size of 68330, so you need to cut 2794 
bytes to see an actual difference in memory usage for a module. Non-SMP 
it is 67741, so there you only need to cut 2205 bytes to get a win.

Every byte counts, except when it doesn't.


  parent reply	other threads:[~2006-04-13  1:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200604071628.30486.vda@ilport.com.ua>
     [not found] ` <200604101716.58463.vda@ilport.com.ua>
     [not found]   ` <1144682807.12177.22.camel@dillow.idleaire.com>
2006-04-11  7:28     ` [PATCH] deinline a few large functions in vlan code v2 Denis Vlasenko
2006-04-11  8:02       ` David S. Miller
2006-04-11  9:49       ` Ingo Oeser
     [not found]         ` <200604111502.52302.vda@ilport.com.ua>
2006-04-11 13:17           ` Ingo Oeser
2006-04-12 19:32             ` [RFD][PATCH] typhoon and core sample for folding away VLAN stuff (was: Re: [PATCH] deinline a few large functions in vlan code v2) Ingo Oeser
2006-04-12 20:10               ` [RFD][PATCH] typhoon and core sample for folding away VLAN stuff Ben Greear
2006-04-12 20:23                 ` Stephen Hemminger
2006-04-12 20:51                 ` David S. Miller
2006-04-13  1:24               ` Dave Dillow [this message]
2006-04-13  8:38                 ` Denis Vlasenko
2006-04-13 15:00                   ` Dave Dillow
2006-04-11 13:59       ` [PATCH] deinline a few large functions in vlan code v2 Dave Dillow
2006-04-12  8:55         ` Denis Vlasenko
2006-04-12 17:18           ` Dave Dillow
2006-04-13  6:04             ` Denis Vlasenko
2006-04-13 14:59               ` Dave Dillow
2006-04-13 11:32             ` Ingo Oeser

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=443DA830.8030209@thedillows.org \
    --to=dave@thedillows.org \
    --cc=davem@davemloft.net \
    --cc=ioe-lkml@rameria.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@axxeo.de \
    --cc=netdev@vger.kernel.org \
    --cc=vda@ilport.com.ua \
    /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).