mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Loongson64: Switch to SYNC_R4K
Date: Thu, 18 Jul 2024 19:28:38 +0200	[thread overview]
Message-ID: <ZplQxmWwujQkBU5w@alpha.franken.de> (raw)
In-Reply-To: <e68b7f44-8a3c-4963-8d95-be8747bf9a61@app.fastmail.com>

On Thu, Jul 18, 2024 at 03:34:30PM +0800, Jiaxun Yang wrote:
> 
> 
> 在2024年7月14日七月 上午10:41,Jiaxun Yang写道:
> > Nowadays SYNC_R4K is performing better than Loongson64's
> > custom sync mechanism.
> >
> > Switch to SYNC_R4K to improve performance and reduce code
> > duplication.
> >
> > Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > ---
> > Last minute for 6.11 :-)
> 
> Hi Thomas,
> 
> Could you please apply this to 6.11 PR, or 6.11 fixes?
> 
> This is technically a left over of previous clock source series, and it does help
> on preventing random RCU stall for multi-node Loongson-3 systems.

if Huacai is ok with it, I'll add it to a second PR for 6.11.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2024-07-18 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14  2:41 Jiaxun Yang
2024-07-14  2:54 ` Huacai Chen
2024-07-14  3:00   ` Jiaxun Yang
2024-07-14  3:02     ` Jiaxun Yang
2024-07-18  7:34 ` Jiaxun Yang
2024-07-18 17:28   ` Thomas Bogendoerfer [this message]
2024-07-23  2:53     ` Huacai Chen
2024-07-23  7:32 ` Thomas Bogendoerfer

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=ZplQxmWwujQkBU5w@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.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 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®