From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, linux-mm@kvack.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v7)
Date: Thu, 3 Apr 2008 11:56:16 -0700 [thread overview]
Message-ID: <6599ad830804031156w79366866yed9f8c3b8acf71fb@mail.gmail.com> (raw)
In-Reply-To: <47F52735.7090502@linux.vnet.ibm.com>
On Thu, Apr 3, 2008 at 11:51 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> >> + * delay_group_leader() ensures that if the group leader is around
> >> + * we need not select a new owner.
> >> + */
> >> + ret = (mm && (atomic_read(&mm->mm_users) > 1) && (mm->owner == p) &&
> >> + !delay_group_leader(p));
> >> + return ret;
> >> +}
> >
> > Ugh. Could you please spell this out a bit more. I find that stuff
> > above really hard to read. Something like:
> >
> > if (!mm)
> > return 0;
> > if (atomic_read(&mm->mm_users) <= 1)
> > return 0;
> > if (mm->owner != p)
> > return 0;
> > if (delay_group_leader(p))
> > return 0;
> > return 1;
> >
>
> The problem with code above is 4 branch instructions and the code I have just 4
> AND operations.
They'll be completely equivalent to the compiler, due to the
short-circuit evaluation of &&
Paul
next prev parent reply other threads:[~2008-04-03 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 17:44 Balbir Singh
2008-04-03 17:58 ` Paul Menage
2008-04-03 18:11 ` Balbir Singh
2008-04-03 18:22 ` Paul Menage
2008-04-03 18:34 ` Balbir Singh
2008-04-03 18:41 ` Paul Menage
2008-04-03 18:48 ` Balbir Singh
2008-04-03 18:25 ` Dave Hansen
2008-04-03 18:30 ` Paul Menage
2008-04-03 18:51 ` Balbir Singh
2008-04-03 18:56 ` Paul Menage [this message]
2008-04-03 19:28 ` Balbir Singh
2008-04-03 18:59 ` Dave Hansen
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=6599ad830804031156w79366866yed9f8c3b8acf71fb@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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