From: David Mosberger <davidm@napali.hpl.hp.com>
To: Chris Wright <chrisw@osdl.org>
Cc: davidm@hpl.hp.com, James Morris <jmorris@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kurt Garloff <garloff@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Smalley <sds@epoch.ncsc.mil>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] [LSM] Rework LSM hooks
Date: Wed, 11 Aug 2004 11:12:11 -0700 [thread overview]
Message-ID: <16666.24955.224034.291755@napali.hpl.hp.com> (raw)
In-Reply-To: <20040811082510.D1924@build.pdx.osdl.net>
>>>>> On Wed, 11 Aug 2004 08:25:10 -0700, Chris Wright <chrisw@osdl.org> said:
>> An alternative solution might be to have a call_likely() macro,
>> where you could predict the most likely target of an indirect
>> call. Perhaps that could help other platforms as well.
Chris> Hmm, the pointers are generally quite static, set once near
Chris> boot time typically, and that's it. Seems like a plausible
Chris> win. Do you have an example of what call_likely() would look
Chris> like?
The macro I had in mind works only for static (compile-time)
predictions, I'm afraid.
--david
next prev parent reply other threads:[~2004-08-11 18:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 8:57 Kurt Garloff
2004-08-10 13:29 ` James Morris
2004-08-10 20:23 ` Chris Wright
2004-08-10 20:27 ` James Morris
2004-08-10 20:43 ` Chris Wright
2004-08-11 1:55 ` James Morris
2004-08-10 14:16 ` James Morris
2004-08-10 15:02 ` Alan Cox
2004-08-10 19:22 ` James Morris
2004-08-10 20:00 ` Chris Wright
2004-08-10 20:07 ` James Morris
2004-08-10 20:12 ` Chris Wright
2004-08-10 20:31 ` James Morris
2004-08-11 8:47 ` David Mosberger
2004-08-11 15:25 ` Chris Wright
2004-08-11 18:12 ` David Mosberger [this message]
2004-08-11 18:16 ` Chris Wright
2004-08-11 22:22 ` Kurt Garloff
2004-08-12 1:23 ` James Morris
2004-08-12 3:58 ` Greg KH
2004-08-12 18:15 ` Chris Wright
2004-08-12 18:17 ` Chris Wright
2004-08-16 14:19 ` Takashi Iwai
2004-08-11 22:19 ` Kurt Garloff
2004-08-12 1:20 ` James Morris
2004-08-12 2:03 ` Kurt Garloff
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=16666.24955.224034.291755@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisw@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=garloff@suse.de \
--cc=greg@kroah.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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®