From: "Sevincer, Abdullah" <abdullah.sevincer@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: quick thread in DLB2
Date: Mon, 4 Sep 2023 19:13:57 +0000 [thread overview]
Message-ID: <BYAPR11MB3158BF100ED49E8E7A9CE45CE9E9A@BYAPR11MB3158.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2363761.yKrmzQ4Hd0@thomas>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Hi Thomas,
That's right we need to create threads on specific CPUs.
________________________________
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Friday, September 1, 2023 7:09 AM
To: Sevincer, Abdullah <abdullah.sevincer@intel.com>
Cc: dev@dpdk.org <dev@dpdk.org>; Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: quick thread in DLB2
Hello Abdullah,
In the DLB2 code, I see a thread is created for a single operation:
In drivers/event/dlb2/pf/base/dlb2_resource.c
pthread_create(&pthread, NULL, &dlb2_pp_profile_func, &dlb2_thread_data[i]);
and just after:
pthread_join(pthread, NULL);
Can we avoid creating this thread?
I guess no, because it must spawn on a specific CPU.
[-- Attachment #2: Type: text/html, Size: 1575 bytes --]
next prev parent reply other threads:[~2023-09-04 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 14:08 Thomas Monjalon
2023-09-04 19:13 ` Sevincer, Abdullah [this message]
2023-09-06 19:45 ` Stephen Hemminger
2023-09-07 22:09 ` Sevincer, Abdullah
2023-09-07 23:37 ` Stephen Hemminger
2023-09-08 7:28 ` Mattias Rönnblom
2023-09-11 14:28 ` Sevincer, Abdullah
2023-09-13 15:48 ` Mattias Rönnblom
2023-09-13 20:56 ` Honnappa Nagarahalli
2023-09-14 8:09 ` Mattias Rönnblom
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=BYAPR11MB3158BF100ED49E8E7A9CE45CE9E9A@BYAPR11MB3158.namprd11.prod.outlook.com \
--to=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).