From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH 2/7] vhost: rename polling mutex
Date: Thu, 29 Feb 2024 13:24:57 +0100 [thread overview]
Message-ID: <20240229122502.2572343-3-maxime.coquelin@redhat.com> (raw)
In-Reply-To: <20240229122502.2572343-1-maxime.coquelin@redhat.com>
This trivial patch fixes a typo in fd's manager polling
mutex name.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
---
lib/vhost/fd_man.c | 8 ++++----
lib/vhost/fd_man.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/vhost/fd_man.c b/lib/vhost/fd_man.c
index 42ce059039..5dde40e51a 100644
--- a/lib/vhost/fd_man.c
+++ b/lib/vhost/fd_man.c
@@ -125,9 +125,9 @@ fdset_add(struct fdset *pfdset, int fd, fd_cb rcb, fd_cb wcb, void *dat)
pthread_mutex_lock(&pfdset->fd_mutex);
i = pfdset->num < MAX_FDS ? pfdset->num++ : -1;
if (i == -1) {
- pthread_mutex_lock(&pfdset->fd_pooling_mutex);
+ pthread_mutex_lock(&pfdset->fd_polling_mutex);
fdset_shrink_nolock(pfdset);
- pthread_mutex_unlock(&pfdset->fd_pooling_mutex);
+ pthread_mutex_unlock(&pfdset->fd_polling_mutex);
i = pfdset->num < MAX_FDS ? pfdset->num++ : -1;
if (i == -1) {
pthread_mutex_unlock(&pfdset->fd_mutex);
@@ -244,9 +244,9 @@ fdset_event_dispatch(void *arg)
numfds = pfdset->num;
pthread_mutex_unlock(&pfdset->fd_mutex);
- pthread_mutex_lock(&pfdset->fd_pooling_mutex);
+ pthread_mutex_lock(&pfdset->fd_polling_mutex);
val = poll(pfdset->rwfds, numfds, 1000 /* millisecs */);
- pthread_mutex_unlock(&pfdset->fd_pooling_mutex);
+ pthread_mutex_unlock(&pfdset->fd_polling_mutex);
if (val < 0)
continue;
diff --git a/lib/vhost/fd_man.h b/lib/vhost/fd_man.h
index cc19937612..2517ae5a9b 100644
--- a/lib/vhost/fd_man.h
+++ b/lib/vhost/fd_man.h
@@ -24,7 +24,7 @@ struct fdset {
struct pollfd rwfds[MAX_FDS];
struct fdentry fd[MAX_FDS];
pthread_mutex_t fd_mutex;
- pthread_mutex_t fd_pooling_mutex;
+ pthread_mutex_t fd_polling_mutex;
int num; /* current fd number of this fdset */
union pipefds {
--
2.43.2
next prev parent reply other threads:[~2024-02-29 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 12:24 [PATCH 0/7] vhost: FD manager improvements Maxime Coquelin
2024-02-29 12:24 ` [PATCH 1/7] vhost: fix VDUSE device destruction failure Maxime Coquelin
2024-02-29 13:31 ` David Marchand
2024-03-04 10:35 ` [PATCH v2] " David Marchand
2024-03-04 15:12 ` Maxime Coquelin
2024-03-05 9:05 ` David Marchand
2024-02-29 12:24 ` Maxime Coquelin [this message]
2024-02-29 13:41 ` [PATCH 2/7] vhost: rename polling mutex David Marchand
2024-02-29 12:24 ` [PATCH 3/7] vhost: make use of FD manager init function Maxime Coquelin
2024-02-29 13:42 ` David Marchand
2024-02-29 12:24 ` [PATCH 4/7] vhost: hide synchronization within FD manager Maxime Coquelin
2024-02-29 12:25 ` [PATCH 5/7] vhost: improve fdset initialization Maxime Coquelin
2024-02-29 12:25 ` [PATCH 6/7] vhost: convert fdset sync to eventfd Maxime Coquelin
2024-02-29 12:25 ` [PATCH 7/7] vhost: improve FD manager logging Maxime Coquelin
2024-03-04 10:35 ` [PATCH 0/7] vhost: FD manager improvements David Marchand
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=20240229122502.2572343-3-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).