From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>,
aneesh.kumar@linux.vnet.ibm.com, linux-mm@kvack.org
Subject: Re: [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS
Date: Thu, 21 Apr 2016 14:15:54 +1000 [thread overview]
Message-ID: <571853FA.5080901@gmail.com> (raw)
In-Reply-To: <1461209879-15044-1-git-send-email-mpe@ellerman.id.au>
On 21/04/16 13:37, Michael Ellerman wrote:
> Testing done by Paul Mackerras has shown that with a modern compiler
> there is no negative effect on code generation from enabling
> STRICT_MM_TYPECHECKS.
>
> So remove the option, and always use the strict type definitions.
>
Should we wait for Aneesh's patches before merging this in. I like the reduction
in the definition of page level metadata so for that
Acked-by: Balbir Singh <bsingharora@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>,
aneesh.kumar@linux.vnet.ibm.com, linux-mm@kvack.org
Subject: Re: [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS
Date: Thu, 21 Apr 2016 14:15:54 +1000 [thread overview]
Message-ID: <571853FA.5080901@gmail.com> (raw)
In-Reply-To: <1461209879-15044-1-git-send-email-mpe@ellerman.id.au>
On 21/04/16 13:37, Michael Ellerman wrote:
> Testing done by Paul Mackerras has shown that with a modern compiler
> there is no negative effect on code generation from enabling
> STRICT_MM_TYPECHECKS.
>
> So remove the option, and always use the strict type definitions.
>
Should we wait for Aneesh's patches before merging this in. I like the reduction
in the definition of page level metadata so for that
Acked-by: Balbir Singh <bsingharora@gmail.com>
--
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 prev parent reply other threads:[~2016-04-21 4:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 3:37 [PATCH] powerpc/mm: Always use STRICT_MM_TYPECHECKS Michael Ellerman
2016-04-21 3:37 ` Michael Ellerman
2016-04-21 4:15 ` Balbir Singh [this message]
2016-04-21 4:15 ` Balbir Singh
2016-04-21 6:36 ` Michael Ellerman
2016-04-21 6:36 ` Michael Ellerman
2016-04-21 9:56 ` Arnd Bergmann
2016-04-21 9:56 ` Arnd Bergmann
2016-04-28 5:27 ` Michael Ellerman
2016-04-28 5:27 ` Michael Ellerman
2016-04-28 5:13 ` Paul Mackerras
2016-04-28 5:13 ` Paul Mackerras
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=571853FA.5080901@gmail.com \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.