From: "George Spelvin" <linux@horizon.com>
To: ebiggers3@gmail.com
Cc: kirill@shutemov.name, linux@horizon.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Bloat caused by unnecessary calls to compound_head()?
Date: 27 Mar 2016 16:33:04 -0400 [thread overview]
Message-ID: <20160327203304.9695.qmail@ns.horizon.com> (raw)
Could you just mark compound_head __pure? That would tell the compiler
that it's safe to re-use the return value as long as there is no memory
mutation in between.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-03-27 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 20:33 George Spelvin [this message]
2016-03-27 20:44 ` Bloat caused by unnecessary calls to compound_head()? Kirill A. Shutemov
-- strict thread matches above, loose matches on Subject: below --
2016-03-26 18:50 Eric Biggers
2016-03-27 19:46 ` Kirill A. Shutemov
2016-04-01 1:33 ` Eric Biggers
2016-04-04 10:39 ` Kirill A. Shutemov
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=20160327203304.9695.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=ebiggers3@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).