> >> that is likely working only for the given very limited set of applications.
> >> Kernel function profiling can potentially achieve the same thing.
> >> Profile the kernel with the set of apps and then prune all cold
> >> functions out of kernel.
> >
> > Right, and are Profile-Guided-Optimizati
Hi!
> > wants to build it and try it out:
> >
> > https://github.com/tzanussi/meta-galileo/blob/daisy/meta-galileo/README
> >
> > It's very much a work-in-progress with a lot of rough edges, but it is a
> > fully functional system on real hardware (Galileo board/Quark processor)
> > with a usable
On Tue, May 6, 2014 at 1:00 PM, Andi Kleen wrote:
>> not quite. I'm saying: no extra optimizations, no GCC changes.
>> Compile kernel as-is. Most functions have a stub for mcount() already.
>> Use it to track whether kernel function was called or not.
>> Collect this data in userspace (as perf alr
> not quite. I'm saying: no extra optimizations, no GCC changes.
> Compile kernel as-is. Most functions have a stub for mcount() already.
> Use it to track whether kernel function was called or not.
> Collect this data in userspace (as perf already does), add few
> more functions that had 'notrace'
On Tue, May 6, 2014 at 8:34 AM, Tom Zanussi wrote:
> On Tue, 2014-05-06 at 08:20 -0700, Alexei Starovoitov wrote:
>> On Tue, May 6, 2014 at 6:34 AM, Tom Zanussi
>> wrote:
>> > On Tue, 2014-05-06 at 09:25 +0200, Richard Weinberger wrote:
>> >> On Tue, May 6, 2014 at 12:25 AM, Andi Kleen wrote:
>
On Tue, 2014-05-06 at 08:20 -0700, Alexei Starovoitov wrote:
> On Tue, May 6, 2014 at 6:34 AM, Tom Zanussi
> wrote:
> > On Tue, 2014-05-06 at 09:25 +0200, Richard Weinberger wrote:
> >> On Tue, May 6, 2014 at 12:25 AM, Andi Kleen wrote:
> >> > There has been a lot of interest recently to run Lin
On Tue, May 6, 2014 at 6:34 AM, Tom Zanussi wrote:
> On Tue, 2014-05-06 at 09:25 +0200, Richard Weinberger wrote:
>> On Tue, May 6, 2014 at 12:25 AM, Andi Kleen wrote:
>> > There has been a lot of interest recently to run Linux on very small
>> > systems,
>> > like Quark systems. These may have
On Tue, 2014-05-06 at 09:25 +0200, Richard Weinberger wrote:
> On Tue, May 6, 2014 at 12:25 AM, Andi Kleen wrote:
> > There has been a lot of interest recently to run Linux on very small
> > systems,
> > like Quark systems. These may have only 2-4MB memory. They are also limited
> > by flash spac
On Tue, May 6, 2014 at 12:25 AM, Andi Kleen wrote:
> There has been a lot of interest recently to run Linux on very small systems,
> like Quark systems. These may have only 2-4MB memory. They are also limited
> by flash space.
>
> One problem on these small system is the size of the network stack.
There has been a lot of interest recently to run Linux on very small systems,
like Quark systems. These may have only 2-4MB memory. They are also limited
by flash space.
One problem on these small system is the size of the network stack.
Currently enabling IPv4 costs about 400k in text, which is p
10 matches
Mail list logo
