From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
linux-security-module@wirex.com
Subject: Re: [PATCH] LSM networking: skb hooks for 2.5.42 (2/7)
Date: Tue, 15 Oct 2002 10:40:14 -0700 (PDT) [thread overview]
Message-ID: <20021015.104014.34145167.davem@redhat.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0210160027110.27676-100000@blackbird.intercode.com.au>
There is no way in hell that you are going to
add a function call for every time we set the
socket owner of a SKB.
That is a critical path and it happens millions upon
millions of times a second on a busy server. Performance
will be penalized by changes like this.
I want all this junk #ifdef'd if it is necessary, in particular
the new member added to sk_buff et al. There is no way this stuff
is going to happen in the default build, at least not in my networking
tree :-)
next prev parent reply other threads:[~2002-10-15 17:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 14:36 [PATCH] LSM networking: skb hooks for 2.5.42 (2/7) James Morris
2002-10-15 17:40 ` David S. Miller [this message]
2002-10-15 18:14 ` Donald Becker
2002-10-15 19:16 ` Greg KH
2002-10-15 19:34 ` David S. Miller
2002-10-15 19:45 ` Greg KH
2002-10-15 19:45 ` David S. Miller
2002-10-15 20:12 ` Greg KH
2002-10-15 20:10 ` David S. Miller
2002-10-15 20:28 ` Greg KH
2002-10-15 20:24 ` David S. Miller
2002-10-16 0:07 ` [RFC] change format of LSM hooks Greg KH
2002-10-16 0:03 ` David S. Miller
2002-10-16 8:15 ` Greg KH
2002-10-16 18:59 ` Greg KH
2002-10-16 19:07 ` Greg KH
2002-10-17 1:41 ` Rusty Russell
2002-10-17 3:33 ` Daniel Phillips
2002-10-17 13:21 ` Christoph Hellwig
2002-10-17 16:55 ` Greg KH
2002-10-19 2:33 ` [PATCH] LSM networking: skb hooks for 2.5.42 (2/7) Keith Owens
2002-10-19 2:54 ` Keith Owens
2002-10-19 3:29 ` Greg KH
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=20021015.104014.34145167.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-security-module@wirex.com \
--cc=netdev@oss.sgi.com \
/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).