mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <cutaway@bellsouth.net>
To: "Denis Vlasenko" <vda@ilport.com.ua>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Observations on x86 process.c
Date: Mon, 13 Jun 2005 12:01:28 -0400	[thread overview]
Message-ID: <008201c57031$2be937a0$2800000a@pc365dualp2> (raw)
In-Reply-To: <200506131726.50264.vda@ilport.com.ua>

----- Original Message ----- 
From: "Denis Vlasenko" <vda@ilport.com.ua>
>
> I am not affected. I compile my kernels with zero alignment.
>
> Not my itch to scratch.

Does some clueless user who needs a custom kernel for something even
understand what you just said?  Probably not...

>
> Do you realize how large linux kernel is? Are you going to optimize all of
it
> by hand?!

Its big, but not as big as some I've worked on.  I'm willing to tune the
"arch" specific stuff where I can do better than the compiler.  A few bytes
here, a few there, pretty soon you got a page back.  BTW, there's just under
100K of fluff zero padding in locked pages because of the way kernel
messages are being 32 byte aligned.  Do you think getting 100K of locked
kernel memory back essentially "for free" is worth taking a shot at?  I do.

>
> People tend to gradually update their systems. Make gcc better, and it
will
> pay back with time. If you want that benefit _now_, then use your better
gcc
> immediately instead of stone age one. Others will take care of themselves.
>
Pretty harsh attitude IMO.  People use compilers because they DO want
someone to take care of some things for them.


  reply	other threads:[~2005-06-13 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 13:02 cutaway
2005-06-13 12:37 ` Jan Engelhardt
2005-06-13 13:43   ` cutaway
2005-06-13 13:18 ` Denis Vlasenko
2005-06-13 15:01   ` cutaway
2005-06-13 14:26     ` Denis Vlasenko
2005-06-13 16:01       ` cutaway [this message]
2005-06-13 16:32   ` cutaway
2005-06-13 16:02     ` Ian Campbell
2005-06-13 19:37       ` cutaway

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='008201c57031$2be937a0$2800000a@pc365dualp2' \
    --to=cutaway@bellsouth.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@ilport.com.ua \
    /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

all inboxes | Powered by JetHome®