public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Greg KH <greg@kroah.com>,
	ksummit-2013-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [Ksummit-2013-discuss] [ATTEND] [ARM ATTEND] kernel data bloat and how to avoid it
Date: Fri, 2 Aug 2013 00:55:15 -0700	[thread overview]
Message-ID: <20130802075514.GZ7656@atomide.com> (raw)
In-Reply-To: <20130731135346.GN5882@titan.lakedaemon.net>

* Jason Cooper <jason@lakedaemon.net> [130731 07:00]:
> On Wed, Jul 31, 2013 at 05:33:51AM -0700, Greg KH wrote:
> > On Wed, Jul 31, 2013 at 12:38:03AM -0700, Tony Lindgren wrote:
> > > Hi all,
> > > 
> > > Probably the biggest kernel data bloat issue is in the ARM land, but
> > > it also seems that it's becoming a Linux generic issue too, so I
> > > guess it could be discussed in either context.
> > 
> > Why is it specific to ARM?  What is so unique to ARM that causes it to
> > "bloat"?
> > 
> > And what exactly do you mean by "bloat"?
> 
> Perhaps he's referring to the multiplatform effort?  You'd get a lot of
> board code that wouldn't be used at each boot.  This should be declining
> though...

Yes that too, device tree and ACPI help there a great deal as we don't
need to build in board specific data for each supported board, but
instead have just one copy of the board specific data come from the
bootloader.

Regards,

Tony

  reply	other threads:[~2013-08-02  7:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  7:38 [ATTEND] [ARM ATTEND] kernel data bloat and how to avoid it Tony Lindgren
2013-07-31 12:33 ` [Ksummit-2013-discuss] " Greg KH
2013-07-31 13:53   ` Jason Cooper
2013-08-02  7:55     ` Tony Lindgren [this message]
2013-08-02  7:53   ` Tony Lindgren
2013-08-02  8:03     ` Felipe Balbi
2013-08-02  8:26       ` Tony Lindgren
2013-08-02  8:11     ` Greg KH
2013-08-02  8:39       ` Tony Lindgren
2013-08-02 12:41     ` Tony Lindgren
2013-08-02 13:24       ` Russell King - ARM Linux
2013-08-05  6:30         ` Tony Lindgren
2013-08-02 19:57     ` Mike Turquette
2013-08-05  6:36       ` Tony Lindgren
2013-07-31 15:21 ` Mel Gorman
2013-08-02  8:13   ` Tony Lindgren
2013-08-02 21:31     ` Matt Sealey
2013-08-03  5:30       ` Olof Johansson
2013-08-05  6:43         ` Tony Lindgren

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=20130802075514.GZ7656@atomide.com \
    --to=tony@atomide.com \
    --cc=greg@kroah.com \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-2013-discuss@lists.linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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