Thread (8 messages) 8 messages, 5 authors, 2007-09-01

Re: [PATCH 5/5] Net: ath5k, kconfig changes

From: "Nick Kossifidis" <mickflemm@gmail.com>
Date: 2007-08-30 22:18:47
Also in: linux-wireless, lkml

2007/8/30, John W. Linville [off-list ref]:
On Thu, Aug 30, 2007 at 04:38:09AM +0300, Nick Kossifidis wrote:
quoted
2007/8/28, Christoph Hellwig [off-list ref]:
quoted
quoted
Also this whole patch seems rather pointless.  It saves only
very little and turns the driver into a complete ifdef maze.
quoted
Also most
people will use 5212 code only, 5211 cards are on some old laptops and
5210, well i couldn't even find  a 5210 for actual testing :P
FWIW, I'd bet dollars to donuts that distros will enable them all
together.

Is saving code space the only reason to turn these off?  How much
space do you save?

Is there some way you can isolate and/or limit the number of ifdef
blocks further?  If so, we might consider a version of this patch
that depends on EMBEDDED or somesuch...?

John
O.K. as a first step i'll limit 5210 code only then, just an option
like "support older 5210 chipsets" which is going to be off by default
instead of 3 options. It's not just saving space, it's also saving
some runtime checks. It's not really a gain in performance though,
most checks are done during initialization and dfs setup, i just
thought it would be usefull to save as much cpu as possible.

-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help