From: Jiri Slaby <jirislaby@gmail•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: sfr@canb•auug.org.au, nhorman@tuxdriver•com,
Heiko Carstens <heiko.carstens@de•ibm.com>,
linux-kernel@vger•kernel.org, oleg@redhat•com,
linuxppc-dev@ozlabs•org, mingo@redhat•com, tglx@linutronix•de,
marcin.slusarz@gmail•com, hpa@zytor•com,
Paul Mackerras <paulus@samba•org>,
akpm@linux-foundation•org, James Morris <jmorris@namei•org>,
torvalds@linux-foundation•org, mingo@elte•hu
Subject: Re: [PATCH v3 16/27] PPC: use helpers for rlimits
Date: Sat, 28 Nov 2009 09:47:01 +0100 [thread overview]
Message-ID: <4B10E385.1030900@gmail.com> (raw)
In-Reply-To: <1259367557.2076.11.camel@pasglop>
On 11/28/2009 01:19 AM, Benjamin Herrenschmidt wrote:
> On Sat, 2009-11-28 at 00:05 +0100, Jiri Slaby wrote:
>> Make sure compiler won't do weird things with limits. E.g. fetching
>> them twice may return 2 different values after writable limits are
>> implemented.
>>
>> I.e. either use newly added rlimit helpers or ACCESS_ONCE if not
>> applicable.
>
> Thanks. I have that already queued up.
Are you sure? The previous version with ACCESS_ONCE was generally
NACKed. This one uses a newly added helper which is much more cleaner
way to do it.
thanks,
--
js
next prev parent reply other threads:[~2009-11-28 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1259363167-9347-1-git-send-email-jslaby@suse.cz>
2009-11-27 23:05 ` [PATCH v3 16/27] PPC: use helpers for rlimits Jiri Slaby
2009-11-28 0:19 ` Benjamin Herrenschmidt
2009-11-28 8:47 ` Jiri Slaby [this message]
2009-11-28 21:16 ` Benjamin Herrenschmidt
2009-11-29 11:06 ` Stephen Rothwell
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=4B10E385.1030900@gmail.com \
--to=jirislaby@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=hpa@zytor$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=marcin.slusarz@gmail$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=mingo@redhat$(echo .)com \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=oleg@redhat$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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