From: Stephen Hemminger <stephen@networkplumber.org>
To: Min Zhou <zhoumin@loongson.cn>
Cc: thomas@monjalon.net, david.marchand@redhat.com,
bruce.richardson@intel.com, anatoly.burakov@intel.com,
qiming.yang@intel.com, Yuying.Zhang@intel.com,
jgrajcia@cisco.com, konstantin.v.ananyev@yandex.ru, dev@dpdk.org,
maobibo@loongson.cn
Subject: Re: [v1 05/24] eal/loongarch: add spinlock operations for LoongArch
Date: Sat, 28 May 2022 08:54:10 -0700 [thread overview]
Message-ID: <20220528085410.62f27ba2@hermes.local> (raw)
In-Reply-To: <20220528093311.123946-6-zhoumin@loongson.cn>
On Sat, 28 May 2022 17:32:52 +0800
Min Zhou <zhoumin@loongson.cn> wrote:
> This patch adds spinlock operations for LoongArch architecture.
> These implementations refer to GLIBC pthread_spin_xxlock(). The
> underlying implementation is based on LoongArch atomic
> instructions (ie, AMSWAP_DB.W).
>
> Signed-off-by: Min Zhou <zhoumin@loongson.cn>
If you supported std atomics, then the g eneric code
could work here.
next prev parent reply other threads:[~2022-05-28 15:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 9:32 [v1 00/24] Support LoongArch architecture Min Zhou
2022-05-28 9:32 ` [v1 01/24] eal/loongarch: add atomic operations for LoongArch Min Zhou
2022-05-28 15:52 ` Stephen Hemminger
2022-05-30 1:00 ` zhoumin
2022-05-28 9:32 ` [v1 02/24] eal/loongarch: add byte order " Min Zhou
2022-05-28 9:32 ` [v1 03/24] eal/loongarch: add cpu cycle " Min Zhou
2022-05-28 9:32 ` [v1 04/24] eal/loongarch: add prefetch " Min Zhou
2022-05-28 9:32 ` [v1 05/24] eal/loongarch: add spinlock " Min Zhou
2022-05-28 15:54 ` Stephen Hemminger [this message]
2022-05-30 1:09 ` zhoumin
2022-05-28 9:32 ` [v1 06/24] eal/loongarch: add cpu flag checks " Min Zhou
2022-05-28 9:32 ` [v1 07/24] eal/loongarch: add dummy vector memcpy " Min Zhou
2022-05-28 9:32 ` [v1 08/24] eal/loongarch: add io operations " Min Zhou
2022-05-28 9:32 ` [v1 09/24] eal/loongarch: add mcslock " Min Zhou
2022-05-28 9:32 ` [v1 10/24] eal/loongarch: add pause " Min Zhou
2022-05-28 9:32 ` [v1 11/24] eal/loongarch: add pflock " Min Zhou
2022-05-28 9:32 ` [v1 12/24] eal/loongarch: add rwlock " Min Zhou
2022-05-28 9:33 ` [v1 13/24] eal/loongarch: add ticketlock " Min Zhou
2022-05-28 9:33 ` [v1 14/24] eal/loongarch: add power " Min Zhou
2022-05-28 9:33 ` [v1 15/24] eal/loongarch: add hypervisor " Min Zhou
2022-05-28 9:33 ` [v1 16/24] mem: add huge page size definition " Min Zhou
2022-05-28 9:33 ` [v1 17/24] eal/linux: set eal base address " Min Zhou
2022-05-28 9:33 ` [v1 18/24] meson: introduce LoongArch architecture Min Zhou
2022-05-28 9:33 ` [v1 19/24] lpm: add dummy vector implementation for LoongArch Min Zhou
2022-05-28 9:33 ` [v1 20/24] ixgbe: " Min Zhou
2022-05-28 9:33 ` [v1 21/24] i40e: " Min Zhou
2022-05-28 9:33 ` [v1 22/24] tap: add system call number " Min Zhou
2022-05-28 9:33 ` [v1 23/24] memif: " Min Zhou
2022-05-28 9:33 ` [v1 24/24] maintainers: claim responsibility " Min Zhou
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=20220528085410.62f27ba2@hermes.local \
--to=stephen@networkplumber.org \
--cc=Yuying.Zhang@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=maobibo@loongson.cn \
--cc=qiming.yang@intel.com \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).