From: Oleg Nesterov <oleg@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Darren Hart <darren@dvhart.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jerome Marchand <jmarchan@redhat.com>,
Larry Woodman <lwoodman@redhat.com>,
Mateusz Guzik <mguzik@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] futex: check PF_KTHREAD rather than !p->mm to filter out kthreads
Date: Sat, 14 Feb 2015 22:54:23 +0100 [thread overview]
Message-ID: <20150214215423.GA18200@redhat.com> (raw)
In-Reply-To: <1423948516.2046.90.camel@stgolabs.net>
On 02/14, Davidlohr Bueso wrote:
>
> On Sat, 2015-02-14 at 21:57 +0100, Oleg Nesterov wrote:
> > Perhaps... but PF_KTHREAD looks self-documented too ;)
>
> Well the idea was to standardize how we check for a kthreads, as opposed
> to improving readability or such. Just a suggestion.
I understand, and of course I won't argue if you add a helper.
I meant that checking for a kthread is already standardized: flags & PF_KTREAD.
Not sure this needs a helper, but I again I won't argue.
Oleg.
next prev parent reply other threads:[~2015-02-14 21:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:05 [PATCH 0/1] futex: check PF_KTHREAD rather than !p->mm to filter out kthreads Oleg Nesterov
2015-02-02 14:05 ` [PATCH 1/1] " Oleg Nesterov
2015-02-04 10:48 ` Peter Zijlstra
2015-02-14 18:01 ` Davidlohr Bueso
2015-02-14 20:57 ` Oleg Nesterov
2015-02-14 21:15 ` Davidlohr Bueso
2015-02-14 21:54 ` Oleg Nesterov [this message]
2015-02-18 17:11 ` [tip:locking/core] locking/futex: Check " tip-bot for Oleg Nesterov
2015-02-02 15:11 ` [PATCH 0/1] futex: check " Peter Zijlstra
2015-02-02 15:13 ` Peter Zijlstra
2015-02-02 15:14 ` Peter Zijlstra
2015-02-02 16:20 ` Oleg Nesterov
2015-02-03 20:09 ` Oleg Nesterov
2015-02-04 11:12 ` Peter Zijlstra
2015-02-04 20:25 ` Oleg Nesterov
2015-02-05 16:27 ` Peter Zijlstra
2015-02-05 18:10 ` Oleg Nesterov
2015-02-06 10:46 ` Peter Zijlstra
2015-02-06 17:04 ` Oleg Nesterov
2015-02-09 20:38 ` Darren Hart
2015-02-10 11:14 ` Oleg Nesterov
2015-02-16 20:13 ` [PATCH 0/1] futex: don't spin waiting for PF_EXITING -> PF_EXITPIDONE transition Oleg Nesterov
2015-02-16 20:13 ` [PATCH 1/1] " Oleg Nesterov
2015-02-27 9:52 ` Peter Zijlstra
2015-02-27 11:54 ` Peter Zijlstra
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=20150214215423.GA18200@redhat.com \
--to=oleg@redhat.com \
--cc=darren@dvhart.com \
--cc=dave@stgolabs.net \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mguzik@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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