From: Arjan van de Ven <arjan@infradead.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@osdl.org>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] ext3_clear_inode(): avoid kfree(NULL)
Date: Sat, 24 Jun 2006 18:55:55 +0200 [thread overview]
Message-ID: <1151168155.3181.69.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <449D6D07.9070901@goop.org>
On Sat, 2006-06-24 at 09:49 -0700, Jeremy Fitzhardinge wrote:
> Arjan van de Ven wrote:
> > nope none at all, at least not on x86/x86-64.
> > (in fact there is no way to help the prediction on those architectures
> > that actually works)
> >
> The branch prediction hint prefixes (2e & 3e) don't work?
last I read they are both actively discouraged and ignored by all
"current" processors from both AMD and Intel. (see the optimization
guide PDF that Intel publishes)
Note: this is based on me reading public documentation, not on me
reading Intel internal stuff or asking the relevant chip architects, so
don't take this as a fully authoritative statement.
next prev parent reply other threads:[~2006-06-24 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606231502.k5NF2jfO007109@hera.kernel.org>
2006-06-23 18:51 ` Jeff Garzik
2006-06-23 21:24 ` Andrew Morton
2006-06-24 12:11 ` Arjan van de Ven
2006-06-24 12:20 ` Steven Rostedt
2006-06-24 12:27 ` Arjan van de Ven
2006-06-24 12:33 ` Steven Rostedt
2006-06-24 12:46 ` Arjan van de Ven
2006-06-24 12:51 ` Steven Rostedt
2006-06-24 12:53 ` Arjan van de Ven
2006-06-24 13:07 ` Steven Rostedt
2006-06-24 14:11 ` Arjan van de Ven
2006-06-24 16:06 ` Nick Piggin
2006-06-24 16:49 ` Jeremy Fitzhardinge
2006-06-24 16:55 ` Arjan van de Ven [this message]
2006-06-24 16:19 ` Pekka Enberg
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=1151168155.3181.69.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®