All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Andrew Jones <ajones@ventanamicro.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	andrew.jones@oss.qualcomm.com, ganboing@gmail.com
Subject: Re: [PATCH] riscv: drop __init from vec_check_unaligned_access_speed_all_cpus
Date: Tue, 16 Jun 2026 11:23:46 +0200	[thread overview]
Message-ID: <87fr2mvnx9.fsf@yellow.woof> (raw)
In-Reply-To: <CAEev2e8AH8W_M4=9N8vLJyvRqwGG=p8O-jVa7tdM3LjCRj=6aw@mail.gmail.com>

Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com> writes:
> I think the difference seems too small here to draw any conclusions.

So the difference is in the noises. That's good to know, thanks for
testing.

> This is only a 4 core CPU.

The probe is done in parallel, so the number of CPUs won't make any
noticeable difference.

I will send patches in this direction instead.

Thanks,
Nam

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Andrew Jones <ajones@ventanamicro.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	andrew.jones@oss.qualcomm.com, ganboing@gmail.com
Subject: Re: [PATCH] riscv: drop __init from vec_check_unaligned_access_speed_all_cpus
Date: Tue, 16 Jun 2026 11:23:46 +0200	[thread overview]
Message-ID: <87fr2mvnx9.fsf@yellow.woof> (raw)
In-Reply-To: <CAEev2e8AH8W_M4=9N8vLJyvRqwGG=p8O-jVa7tdM3LjCRj=6aw@mail.gmail.com>

Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com> writes:
> I think the difference seems too small here to draw any conclusions.

So the difference is in the noises. That's good to know, thanks for
testing.

> This is only a 4 core CPU.

The probe is done in parallel, so the number of CPUs won't make any
noticeable difference.

I will send patches in this direction instead.

Thanks,
Nam

  reply	other threads:[~2026-06-16  9:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 16:24 [PATCH] riscv: drop __init from vec_check_unaligned_access_speed_all_cpus Anirudh Srinivasan
2026-06-12 16:24 ` Anirudh Srinivasan
2026-06-12 21:23 ` Nam Cao
2026-06-12 21:23   ` Nam Cao
2026-06-15 17:22   ` Anirudh Srinivasan
2026-06-15 17:22     ` Anirudh Srinivasan
2026-06-16  9:23     ` Nam Cao [this message]
2026-06-16  9:23       ` Nam Cao

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=87fr2mvnx9.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=ganboing@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.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.