>> Will the compilation be a bit quicker when extra data processing
>> could be omitted?
>
> Why would you care more about the time it takes to compile the kernel,
> than the time it takes for executing it?
I am also interested in the evolution of compilation time frames.
> Benchmarks are all a
>> Can the software areas distinguished where such special handling matters?
>
> No idea.
I would like to point another example out.
> That's something you are going to have to figure out on your own.
How do you think about information from an other clarification request
for the topic “caif: U
On Mon, 4 Dec 2017 10:00:54 +0100
SF Markus Elfring wrote:
> > Why would you compile the kernel without optimization?
>
> Can another reason be occasionally still relevant?
No.
>
> Will the compilation be a bit quicker when extra data processing
> could be omitted?
Why would you care more
> Why would you compile the kernel without optimization?
Can another reason be occasionally still relevant?
Will the compilation be a bit quicker when extra data processing
could be omitted?
> There's many places in the kernel that WILL NOT BUILD without optimization.
Would you like to keep th
On Sun, 3 Dec 2017 22:56:51 +0100
SF Markus Elfring wrote:
> Can the software areas distinguished where such special handling matters?
No idea. That's something you are going to have to figure out on your
own.
-- Steve
> Why would you compile the kernel without optimization?
I would like to see how big an effect finally is in such a build configuration
after specific source code adjustments.
> There's many places in the kernel that WILL NOT BUILD without optimization.
I did not really know this detail so far.
On Sun, 3 Dec 2017 15:17:32 +
Trond Myklebust wrote:
> > I would like to check corresponding build results then without extra
> > optimisation applied by the compiler.
> > But I got surprised by error messages for a command like the
> > following.
> >
> > elfring@Sonne:~/Projekte/Linux/next-
On Sun, 2017-12-03 at 15:15 +0100, SF Markus Elfring wrote:
> Hello,
>
> I came along some software modules where I suggested source code
> adjustments.
>
> Example:
> nfs/write: Use common error handling code in
> nfs_lock_and_join_requests()
>
> https://lkml.org/lkml/2017/11/7/599
> https://pa
8 matches
Mail list logo
