From: Ralf Baechle <ralf@linux-mips.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Daney <ddaney.cavm@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Single MIPS kernel
Date: Thu, 23 Oct 2014 01:22:34 +0200 [thread overview]
Message-ID: <20141022232233.GF12502@linux-mips.org> (raw)
In-Reply-To: <1414016140.5994.9.camel@decadent.org.uk>
On Wed, Oct 22, 2014 at 11:15:40PM +0100, Ben Hutchings wrote:
> >
> > That's probably more of an implementation detail. I'm more concerned about
> > the overall bloat. I think many embedded users are so addivted to benchmark
> > results that this going to make or break the whole scheme.
>
> If you can make relocation a configuration option (as on x86), it would
> allow distributions to build multiplatform kernels without preventing
> embedded users from building a kernel optimised for their specific
> system. But I know very little about MIPS or how intrusive the changes
> for relocation would have to be. Perhaps it would be too much of a
> maintenance burden to make this an option.
The scope of the changes is relativly limited - we're much more concerned
about the impact on binary size, memory size or performance of the
various approaches under discussion.
I wonder kernels for which platforms would Debian want to unify?
Ralf
next prev parent reply other threads:[~2014-10-22 23:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 8:34 Single MIPS kernel Ralf Baechle
2014-10-22 10:53 ` John Crispin
2014-10-22 17:36 ` Florian Fainelli
2014-10-22 17:56 ` David Daney
2014-10-22 19:05 ` Ralf Baechle
2014-10-22 19:19 ` Maciej W. Rozycki
2014-10-22 20:42 ` Ralf Baechle
2014-10-22 21:10 ` David Daney
2014-10-22 21:53 ` James Hogan
2014-10-22 21:53 ` James Hogan
2014-10-22 22:18 ` David Daney
2014-10-22 18:03 ` David Daney
2014-10-22 19:20 ` Ralf Baechle
2014-10-22 22:15 ` Ben Hutchings
2014-10-22 23:22 ` Ralf Baechle [this message]
2014-10-23 1:02 ` Ben Hutchings
2014-10-23 3:13 ` Joshua Kinard
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=20141022232233.GF12502@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ben@decadent.org.uk \
--cc=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.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