public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: lwn@lwn.net, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@mandriva.com>
Subject: Re: Fw: Top 100 inline functions (make allyesconfig) was Re: [ANNOUNCE] pahole and other DWARF2 utilities
Date: Sun, 05 Nov 2006 14:32:17 +0800	[thread overview]
Message-ID: <1162708337.3374.21.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20061104132050.4950866b.akpm@osdl.org>

On Sat, 2006-11-04 at 13:20 -0800, Andrew Morton wrote:
> cfi_build_cmd() is nutty. 

Damn right it's nutty. Imagine the number of ways you can wire up 1-8
flash chips in either 8-bit or 16-bit mode to a bus which is between 8
and 64 bits wide. Deal with it in software, with a "chip driver"
abstraction which knows what data to put at which address on each
_chip_, and which needs to calculate the corresponding bus data/address.

In the sensible case where you build in support for what you have -- one
interleave, one mode, one bus size -- it's simple. And that's why it's
inline. This is one of the cases where 'allyesconfig' just doesn't make
much sense.

I'm not entirely averse to taking it out-of-line, but show me data on
the interesting case rather than the allyesconfig case.

And tell me about it in about two weeks' time when the sky stops falling
on my head and I get to go home. :)

-- 
dwmw2

       reply	other threads:[~2006-11-05  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061104132050.4950866b.akpm@osdl.org>
2006-11-05  6:32 ` David Woodhouse [this message]
2006-11-05 16:43   ` Fw: Top 100 inline functions (make allyesconfig) was Re: [ANNOUNCE] pahole and other DWARF2 utilities Arnaldo Carvalho de Melo

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=1162708337.3374.21.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=acme@mandriva.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lwn@lwn.net \
    /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