From: David Laight <David.Laight@ACULAB.COM>
To: 'Kent Overstreet' <kent.overstreet@gmail.com>
Cc: 'Marcelo Ricardo Leitner' <marcelo.leitner@gmail.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-sctp@vger.kernel.org'" <linux-sctp@vger.kernel.org>,
'Eric Biggers' <ebiggers@kernel.org>,
'Catalin Marinas' <catalin.marinas@arm.com>,
'Andrew Morton' <akpm@linux-foundation.org>,
'Neil Horman' <nhorman@tuxdriver.com>
Subject: RE: [PATCH 00/13] lib/generic-radix-tree: genradix bug fix and optimisations.
Date: Wed, 26 Aug 2020 08:37:39 +0000 [thread overview]
Message-ID: <3e60559ff056423dbd19bb5e2eecc2e9@AcuMS.aculab.com> (raw)
In-Reply-To: <425b461bdd4c429c905f99d2ab7451f2@AcuMS.aculab.com>
From: David Laight
> Sent: 26 August 2020 08:36
...
> I'm going to try marking the lookup functions with '__attribute__ ((pure))'.
> That should help the sctp code that does repeated SCTP_SI().
> In reality I want to mark them __attribute__ ((const)) - including the
> inline wrappers, but that isn't allowed if they read memory.
Neither pure nor const makes any difference.
Even to code that like:
if (SCTP_SO(...)->ext)
SCTP_SO(...)->ext->foo = 0;
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-08-26 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 14:52 [PATCH 00/13] lib/generic-radix-tree: genradix bug fix and optimisations David Laight
2020-08-25 15:41 ` 'Marcelo Ricardo Leitner'
2020-08-25 16:00 ` David Laight
2020-08-25 16:32 ` Kent Overstreet
2020-08-26 7:35 ` David Laight
2020-08-26 8:37 ` David Laight [this message]
2020-08-26 9:56 ` David Laight
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=3e60559ff056423dbd19bb5e2eecc2e9@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=ebiggers@kernel.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=nhorman@tuxdriver.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).