From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Shi-Wu, Lo（Gmail）" <shiwulo@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, Mel Gorman <mgorman@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: A new spinlock for multicore (>16) platform
Date: Sat, 20 Jul 2024 14:08:58 +0700 [thread overview]
Message-ID: <ZptiivWvB97Nhyw2@archie.me> (raw)
In-Reply-To: <CAOpXEOyC4WyOuCbGpoVoqtEMG4emR+wSXDKODqULYN0EpLEKdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
On Wed, Jul 17, 2024 at 02:10:59AM +0800, Shi-Wu, Lo（Gmail） wrote:
> Dear Linux Contributors,
> Yesterday, I did not inform you that I added the mailing list of the
> Operating Systems Laboratory at National Chung Cheng University,
> Taiwan, to this discussion. I apologize for this discourtesy. The
> mailing list has since been removed.
>
> Could you please give me more advice? For example, should we implement
> RON in the kernel under the current circumstances? Or should we
> conduct more research before implementing RON in the kernel?
> Additionally, is the current approach (where the superuser sets the
> routing table) feasible?
Show us the actual code (send the actual patch series). For information
on how to submit patches, see Documentation/process/submitting-patches.rst
in the kernel sources.
Bye!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-07-20 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 17:07 Shi-Wu, Lo（Gmail）
2024-07-14 23:45 ` Bagas Sanjaya
2024-07-15 2:08 ` Waiman Long
2024-07-15 10:01 ` Shi-Wu, Lo（Gmail）
2024-07-15 9:54 ` Peter Zijlstra
2024-07-15 10:33 ` Shi-Wu, Lo（Gmail）
2024-07-16 18:10 ` Shi-Wu, Lo（Gmail）
2024-07-20 7:08 ` Bagas Sanjaya [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=ZptiivWvB97Nhyw2@archie.me \
--to=bagasdotme@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shiwulo@gmail.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=will@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®