mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Indrek Kruusa <indrek.kruusa@gmail.com>
To: Wilken Gottwalt <wilken.gottwalt@posteo.net>
Cc: Nguyen Minh Tien <tien.nguyenminh@embeddedlinux.blog>,
	Bjorn Andersson <andersson@kernel.org>,
	Chen-Yu Tsai <wens@kernel.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	linux-remoteproc@vger.kernel.org, linux-sunxi@lists.linux.dev,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] hwspinlock: sun6i: Allwinner D1 and T113 support
Date: Thu, 22 Oct 2026 22:54:26 +0300	[thread overview]
Message-ID: <20261022195447.2007440-1-indrek.kruusa@gmail.com> (raw)
In-Reply-To: <20261022211952.7293f8b6@posteo.net>

Hi Wilken,

I observed something like a 4.5x slowdown - around 12 us per take/free on
the C906: the loop with the lock runs at ~14.7 us/iteration, the same loop
without it at ~3.3 us.

So yes, the effect is material.

Greetings,
Indrek

      reply	other threads:[~2026-10-22 19:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  2:56 Nguyen Minh Tien
2026-09-27  2:56 ` [PATCH 1/3] hwspinlock: sun6i: Get the clock and the reset without names Nguyen Minh Tien
2026-09-27  2:56 ` [PATCH 2/3] dt-bindings: hwlock: sun6i: Add compatible for Allwinner D1 Nguyen Minh Tien
2026-09-28 16:51   ` Conor Dooley
2026-09-27  2:56 ` [PATCH 3/3] riscv: dts: allwinner: d1-t113: Add the hardware spinlock Nguyen Minh Tien
2026-09-27 11:27   ` Wilken Gottwalt
2026-09-30 13:02     ` Nguyen Minh Tien
2026-09-30 14:05       ` Wilken Gottwalt
2026-10-02  7:32         ` Conor Dooley
2026-10-02  7:48           ` Wilken Gottwalt
2026-10-02  7:50             ` Chen-Yu Tsai
2026-10-02  8:37             ` Conor Dooley
2026-10-02  7:48           ` Chen-Yu Tsai
2026-10-22 19:01 ` [PATCH 0/3] hwspinlock: sun6i: Allwinner D1 and T113 support Indrek Kruusa
2026-10-22 19:19   ` Wilken Gottwalt
2026-10-22 19:54     ` Indrek Kruusa [this message]

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=20261022195447.2007440-1-indrek.kruusa@gmail.com \
    --to=indrek.kruusa@gmail.com \
    --cc=andersson@kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=tien.nguyenminh@embeddedlinux.blog \
    --cc=wens@kernel.org \
    --cc=wilken.gottwalt@posteo.net \
    /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
all inboxes | Powered by JetHome®