From: Greg KH <greg@kroah.com>
To: Tony Lindgren <tony@atomide.com>
Cc: 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: Wed, 31 Jul 2013 05:33:51 -0700 [thread overview]
Message-ID: <20130731123351.GA30474@kroah.com> (raw)
In-Reply-To: <20130731073802.GT7656@atomide.com>
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"?
> Basically the data bloat issue is there for the arch code and drivers
> and may not show up initially until things have headed the wrong way for
> too long.
What do you mean by this? You seem to be very vague here.
greg k-h
next prev parent reply other threads:[~2013-07-31 12:32 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 ` Greg KH [this message]
2013-07-31 13:53 ` [Ksummit-2013-discuss] " Jason Cooper
2013-08-02 7:55 ` Tony Lindgren
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=20130731123351.GA30474@kroah.com \
--to=greg@kroah.com \
--cc=ksummit-2013-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
/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