public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: James Morris <jmorris@redhat.com>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Large inlines in include/linux/skbuff.h
Date: Thu, 22 Apr 2004 21:24:11 +0200	[thread overview]
Message-ID: <40881BDB.4050909@cosmosbay.com> (raw)
In-Reply-To: <200404221927.34717.vda@port.imtp.ilyichevsk.odessa.ua>

Denis Vlasenko wrote:

>
>>
>>If this a specialized machine, with a small program that mostly uses
>>recv() & send() syscalls, then, inlining functions is a gain, since
>>icache may have a 100% hit ratio. Optimization guidelines are good for
>>the common cases, not every cases.
>>    
>>
>
>And if it is NOT a specialized machine? icache miss will nullify
>any speed advantages, while you still pay space penalty.
>We don't need to pay for at least ~250 kbytes wasted overall
>in allyesconfig kernel for each and every specialized
>setup conceivable, IMHO.
>  
>
The point is : if this IS a specialized machine, then the kernel is 
custom one, not allyesconfig.

This is imho what I do for specialized machines, and yes, I even inline 
some specific functions, like fget() and others.

But I didnt asked to not doing the un-inlining, I was just reminding 
that some guys (like me) are doing micro-optimizations that 'seem' to go 
against Optimizations guidelines from intel or AMD.

Eric


  parent reply	other threads:[~2004-04-22 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1NvJL-1QO-9@gated-at.bofh.it>
     [not found] ` <1NAJr-61F-3@gated-at.bofh.it>
2004-04-22 14:59   ` Large inlines in include/linux/skbuff.h Andi Kleen
2004-04-22 15:15     ` James Morris
2004-04-22 15:37       ` Eric Dumazet
     [not found]         ` <200404221927.34717.vda@port.imtp.ilyichevsk.odessa.ua>
2004-04-22 19:24           ` Eric Dumazet [this message]
2004-04-22 22:23       ` Andi Kleen
2004-04-22 22:25         ` David S. Miller
2004-04-22 22:34           ` Andi Kleen
2004-04-22 22:35             ` David S. Miller
     [not found]   ` <1NRqX-2GI-15@gated-at.bofh.it>
     [not found]     ` <1NRqX-2GI-13@gated-at.bofh.it>
2004-04-22 19:51       ` Andi Kleen
2004-04-21 19:26 Denis Vlasenko
2004-04-22  0:47 ` James Morris
     [not found]   ` <200404221756.46240.vda@port.imtp.ilyichevsk.odessa.ua>
2004-04-22 18:36     ` David S. Miller
     [not found]       ` <200404222239.34760.vda@port.imtp.ilyichevsk.odessa.ua>
2004-04-22 22:10         ` David S. Miller

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=40881BDB.4050909@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=ak@muc.de \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.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