Le 02/05/2021 à 06:56, Nicholas Piggin a écrit :
This reduces TLB misses by nearly 30x on a `git diff` workload on a
2-node POWER9 (59,800 -> 2,100) and reduces CPU cycles by 0.54%, due
to vfs hashes being allocated with 2MB pages.
Acked-by: Michael Ellerman
Signed-off-by: Nicholas Piggin
, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Nicholas-Piggin/powerpc-64s-radix-Enable-huge-vmalloc-mappings/20210502-125808
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Nicholas-Piggin/powerpc-64s-radix-Enable-huge-vmalloc-mappings/20210502-125808
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc
Excerpts from Christophe Leroy's message of May 2, 2021 5:34 pm:
>
>
> Le 02/05/2021 à 06:56, Nicholas Piggin a écrit :
>> This reduces TLB misses by nearly 30x on a `git diff` workload on a
>> 2-node POWER9 (59,800 -> 2,100) and reduces CPU cycles by 0.54%, due
>> to vfs hashes being allocated
This reduces TLB misses by nearly 30x on a `git diff` workload on a
2-node POWER9 (59,800 -> 2,100) and reduces CPU cycles by 0.54%, due
to vfs hashes being allocated with 2MB pages.
Acked-by: Michael Ellerman
Signed-off-by: Nicholas Piggin
---
Since v1:
- Don't define MODULES_VADDR which has
suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Nicholas-Piggin/powerpc-64s-radix-Enable-huge-vmalloc-mappings/20210502-190249
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config
Nicholas Piggin writes:
> Excerpts from Naveen N. Rao's message of April 27, 2021 11:43 pm:
>> Nicholas Piggin wrote:
>>> The paravit queued spinlock slow path adds itself to the queue then
>>> calls pv_wait to wait for the lock to become free. This is implemented
>>> by calling H_CONFER to
On Wed, Apr 29, 2020 at 10:57:16AM +1000, Nicholas Piggin wrote:
> Excerpts from Segher Boessenkool's message of April 29, 2020 9:40 am:
> I blame toolchain for -mabi=elfv2 ! And also some blame on ABI document
> which is called ELF V2 ABI rather than ELF ABI V2 which would have been
>
On Tue, Apr 28, 2020 at 09:25:17PM +1000, Nicholas Piggin wrote:
> Provide an option to use ELFv2 ABI for big endian builds. This works on
> GCC and clang (since 2014). It is less well tested and supported by the
> GNU toolchain, but it can give some useful advantages of the ELFv2 ABI
> for BE
Le 02/05/2021 à 13:00, Nicholas Piggin a écrit :
This reduces TLB misses by nearly 30x on a `git diff` workload on a
2-node POWER9 (59,800 -> 2,100) and reduces CPU cycles by 0.54%, due
to vfs hashes being allocated with 2MB pages.
Acked-by: Michael Ellerman
Signed-off-by: Nicholas Piggin
There is some disconnect between commit 8a18cc0c2c36 ("powerpc: Only
disable HAVE_EFFICIENT_UNALIGNED_ACCESS on POWER7 little endian") and
commit a75c380c7129 ("powerpc: Enable DCACHE_WORD_ACCESS on ppc64le").
The first defines HAVE_EFFICIENT_UNALIGNED_ACCESS for the purpose of
enabling
Le 03/05/2021 à 07:39, Jordan Niethe a écrit :
On Thu, Apr 29, 2021 at 3:04 PM Christophe Leroy
wrote:
Le 29/04/2021 à 05:15, Jordan Niethe a écrit :
If MODULES_{VADDR,END} are not defined set them to VMALLOC_START and
VMALLOC_END respectively. This reduces the need for special cases.
On Sat, May 01, 2021 at 07:41:53PM -0700, Joe Perches wrote:
> Why not raise the minimum gcc compiler version even higher?
The latest GCC 5 release is only three and a half years old. Do you
really want to require bleeding edge tools?
Segher
On Sun, May 2, 2021 at 1:38 PM Segher Boessenkool
wrote:
>
> The point is, you inconvenience users if you require a compiler version
> they do not already have. Five years might be fine, but three years is
> not.
So this should be our main issue - not how old a compiler is, but how
our compiler
On Sun, May 02, 2021 at 12:15:38AM +0900, Masahiro Yamada wrote:
> The current minimum GCC version is 4.9 except ARCH=arm64 requiring
> GCC 5.1.
>
> When we discussed last time, we agreed to raise the minimum GCC version
> to 5.1 globally. [1]
>
> I'd like to propose GCC 5.2 to clean up
On Sun, 2021-05-02 at 13:30 -0500, Segher Boessenkool wrote:
> On Sat, May 01, 2021 at 07:41:53PM -0700, Joe Perches wrote:
> > Why not raise the minimum gcc compiler version even higher?
On Sun, 2021-05-02 at 13:37 -0500, Segher Boessenkool wrote:
> Everyone should always use an as new release
On Sun, May 02, 2021 at 01:00:28PM -0700, Joe Perches wrote:
> On Sun, 2021-05-02 at 13:30 -0500, Segher Boessenkool wrote:
> > On Sat, May 01, 2021 at 07:41:53PM -0700, Joe Perches wrote:
> > > Why not raise the minimum gcc compiler version even higher?
>
> On Sun, 2021-05-02 at 13:37 -0500,
On Sun, 2021-05-02 at 15:32 -0500, Segher Boessenkool wrote:
> On Sun, May 02, 2021 at 01:00:28PM -0700, Joe Perches wrote:
[]
> > Perhaps 8 might be best as that has a __diag warning control mechanism.
>
> I have no idea what you mean?
? read the last bit of compiler-gcc.h
On 02/05/2021 23.32, Segher Boessenkool wrote:
On Sun, May 02, 2021 at 01:00:28PM -0700, Joe Perches wrote:
On Sun, 2021-05-02 at 13:30 -0500, Segher Boessenkool wrote:
On Sat, May 01, 2021 at 07:41:53PM -0700, Joe Perches wrote:
Why not raise the minimum gcc compiler version even higher?
On Thu, Apr 29, 2021 at 3:04 PM Christophe Leroy
wrote:
>
>
>
> Le 29/04/2021 à 05:15, Jordan Niethe a écrit :
> > If MODULES_{VADDR,END} are not defined set them to VMALLOC_START and
> > VMALLOC_END respectively. This reduces the need for special cases. For
> > example, powerpc's module_alloc()
On Thu, Apr 29, 2021 at 5:32 PM Christophe Leroy
wrote:
>
>
>
> Le 29/04/2021 à 05:15, Jordan Niethe a écrit :
> > From: Russell Currey
> >
> > The set_memory_{ro/rw/nx/x}() functions are required for
> > STRICT_MODULE_RWX, and are generally useful primitives to have. This
> > implementation is
On Sun, May 02, 2021 at 02:08:31PM -0700, Linus Torvalds wrote:
> What is relevant is what version of gcc various distributions actually
> have reasonably easily available, and how old and relevant the
> distributions are. We did decide that (just as an example) RHEL 7 was
> too old to worry about
Excerpts from Christophe Leroy's message of May 3, 2021 3:11 am:
>
>
> Le 02/05/2021 à 13:00, Nicholas Piggin a écrit :
>> This reduces TLB misses by nearly 30x on a `git diff` workload on a
>> 2-node POWER9 (59,800 -> 2,100) and reduces CPU cycles by 0.54%, due
>> to vfs hashes being allocated
Excerpts from Segher Boessenkool's message of May 3, 2021 3:55 am:
> On Wed, Apr 29, 2020 at 10:57:16AM +1000, Nicholas Piggin wrote:
>> Excerpts from Segher Boessenkool's message of April 29, 2020 9:40 am:
>> I blame toolchain for -mabi=elfv2 ! And also some blame on ABI document
>> which is
On Sun, May 02, 2021 at 02:23:01PM -0700, Joe Perches wrote:
> On Sun, 2021-05-02 at 15:32 -0500, Segher Boessenkool wrote:
> > On Sun, May 02, 2021 at 01:00:28PM -0700, Joe Perches wrote:
> []
> > > Perhaps 8 might be best as that has a __diag warning control mechanism.
> >
> > I have no idea
Excerpts from Michal Suchánek's message of May 3, 2021 2:57 am:
> On Tue, Apr 28, 2020 at 09:25:17PM +1000, Nicholas Piggin wrote:
>> Provide an option to use ELFv2 ABI for big endian builds. This works on
>> GCC and clang (since 2014). It is less well tested and supported by the
>> GNU toolchain,
26 matches
Mail list logo
