netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: ioe-lkml@rameria.de, davem@davemloft.net,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] scm: fold __scm_send() into scm_send()
Date: Mon, 13 Mar 2006 14:13:05 -0800	[thread overview]
Message-ID: <20060313141305.0cd4fe97.akpm@osdl.org> (raw)
In-Reply-To: <20060313202242.GC27761@kvack.org>

Benjamin LaHaise <bcrl@kvack.org> wrote:
>
> On Mon, Mar 13, 2006 at 09:05:31PM +0100, Ingo Oeser wrote:
> > From: Ingo Oeser <ioe-lkml@rameria.de>
> > 
> > Fold __scm_send() into scm_send() and remove that interface completly
> > from the kernel.
> 
> Whoa, what are you doing here?
>

scm_send() and scm_recv() are already uninlined in Dave's tree - this patch
does further consolidation.

>  Uninlining scm_send() is a Bad Thing to do 
> given that scm_send() is in the AF_UNIX hot path.

scm_send() and scm_recv() are in _two_ AF_UNIX hotpaths...

  reply	other threads:[~2006-03-13 22:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603130139.k2D1dpSQ021279@shell0.pdx.osdl.net>
     [not found] ` <20060312.180802.13404061.davem@davemloft.net>
2006-03-13 20:05   ` [PATCH] scm: fold __scm_send() into scm_send() Ingo Oeser
2006-03-13 20:22     ` Benjamin LaHaise
2006-03-13 22:13       ` Andrew Morton [this message]
2006-03-14  1:31     ` Andrew Morton
2006-03-20 11:44       ` Ingo Oeser
2006-03-20 20:18         ` Chris Wright
2006-03-20 21:36           ` Chris Wright
2006-03-20 22:31             ` Andrew Morton
2006-03-20 23:15               ` Chris Wright
2006-03-21 13:32                 ` Stephen Smalley
2006-03-21 13:42                   ` Stephen Smalley
2006-04-06 17:52                     ` Xiaolan Zhang
2006-03-20 23:28             ` David S. Miller
2006-03-20 23:43               ` Chris Wright
2006-03-21  0:37               ` James Morris
2006-03-21  0:50                 ` 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=20060313141305.0cd4fe97.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bcrl@kvack.org \
    --cc=davem@davemloft.net \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).