lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Minlan Wang via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] urcu workqueue thread uses 99% of cpu while workqueue is empty
Date: Thu, 16 Jun 2022 03:09:44 -0400	[thread overview]
Message-ID: <20220616070944.GA246238@localhost.localdomain> (raw)
In-Reply-To: <396090936.61897.1655302558168.JavaMail.zimbra@efficios.com>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

Hi, Mathieu,
We updated our kernel as your guide, now it's 3.10.0-1160.66.1.el7.x86_64, and
the issue still exists.

On Wed, Jun 15, 2022 at 10:15:58AM -0400, Mathieu Desnoyers wrote:
> ----- On Jun 14, 2022, at 11:49 PM, Minlan Wang wangminlan@szsandstone.com wrote:
> 
> One more thing: did you apply any changes on top of the v0.12.1 userspace rcu tag ?
We make no change into the userspace-rcu-latest-0.12.tar.bz2 tarball, we just
place the extracted directory into our code repository.

> 
> Also, can you provide the output of "./configure" on your system ? I'm also interested
> in knowing the contents of include/urcu/config.h after building liburcu.
This is the Makefile we use to build urcu:
---
CUR_DIR = $(shell pwd)
TOP_DIR = $(abspath $(CUR_DIR)/../)
URCU_DIR = $(abspath $(TOP_DIR)/thirdparty/usr)

urcu:
	cd $(TOP_DIR)/thirdparty &&	\
	cd userspace-rcu-0.12.1	&& \
	export CFLAGS="-fPIC -g -O0" && \
	./configure --prefix=$(URCU_DIR) && \
	make				&& \
	make install			&& \
	cp src/workqueue.h $(URCU_DIR)/include/urcu/

I put the these things into the attachment config.tar.gz:
1. configure: the configure script under userspace-rcu-0.12.1/
2. config.log: the configure log after urcu build
3. config.h: include/urcu/config.h after building
4. Makefile: the Makefile recipe we use to build urcu

Thanks for your help,
Minlan

[-- Attachment #2: config.tar.gz --]
[-- Type: application/gzip, Size: 136921 bytes --]

[-- Attachment #3: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2022-06-16  7:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  3:55 [lttng-dev] urcu workqueue thread uses 99% of cpu while workqueue is empty Minlan Wang via lttng-dev
2022-06-14 13:39 ` Mathieu Desnoyers via lttng-dev
2022-06-14 13:40   ` Mathieu Desnoyers via lttng-dev
2022-06-14 14:19 ` Mathieu Desnoyers via lttng-dev
2022-06-14 15:53 ` Mathieu Desnoyers via lttng-dev
2022-06-15  3:49   ` Minlan Wang via lttng-dev
2022-06-15 13:35     ` Mathieu Desnoyers via lttng-dev
2022-06-15 14:15     ` Mathieu Desnoyers via lttng-dev
2022-06-16  7:09       ` Minlan Wang via lttng-dev [this message]
2022-06-16  8:09       ` Minlan Wang via lttng-dev
2022-06-17 13:37         ` Mathieu Desnoyers via lttng-dev
2022-06-21  3:52           ` Minlan Wang via lttng-dev
2022-06-21 13:12             ` [lttng-dev] ***UNCHECKED*** " Mathieu Desnoyers via lttng-dev
2022-06-22  7:45               ` Minlan Wang via lttng-dev
2022-06-22 13:19                 ` [lttng-dev] ***UNCHECKED*** " Mathieu Desnoyers via lttng-dev
2022-06-22 20:28                   ` Mathieu Desnoyers via lttng-dev
2022-06-22 20:52                     ` Mathieu Desnoyers via lttng-dev
2022-06-23  9:08                       ` Minlan Wang via lttng-dev
     [not found]                   ` <20220623034528.GA271179@localhost.localdomain>
2022-06-23  3:57                     ` Minlan Wang via lttng-dev
2022-06-23 14:09                       ` Mathieu Desnoyers via lttng-dev
2022-06-24  6:21                         ` Minlan Wang via lttng-dev
2022-06-23  8:36                   ` [lttng-dev] [PART 4/4] " Minlan Wang via lttng-dev

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=20220616070944.GA246238@localhost.localdomain \
    --to=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=wangminlan@szsandstone.com \
    /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).