From: Jens Axboe <axboe@kernel.dk>
To: Bruce Cran <bruce@cran.org.uk>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Use pthread_self instead of thr_self on BSD
Date: Sat, 30 Jul 2011 13:23:52 +0200 [thread overview]
Message-ID: <4E33E9C8.1060209@kernel.dk> (raw)
In-Reply-To: <4E33E84F.2060705@cran.org.uk>
On 2011-07-30 13:17, Bruce Cran wrote:
> On 30/07/2011 11:55, Jens Axboe wrote:
>> On 2011-07-30 11:43, Bruce Cran wrote:
>>> The attached patch uses pthread_self to get the thread ID instead of the
>>> non-POSIX thr_self This fixes a compiler warning on FreeBSD.
>> Does pthread_self() return a thread ID in the PID name space, so to
>> speak?
>>
>
> Hmm no, it doesn't seem to. In that case <sys/thr.h> should probably be
> included to get the definition of thr_self().
I suspected as much, most OS' will return a unique ID but not something
you can otherwise use. How about the below?
diff --git a/os/os-freebsd.h b/os/os-freebsd.h
index fad051f..317d403 100644
--- a/os/os-freebsd.h
+++ b/os/os-freebsd.h
@@ -4,6 +4,7 @@
#include <errno.h>
#include <sys/sysctl.h>
#include <sys/disk.h>
+#include <sys/thr.h>
#include "../file.h"
diff --git a/os/os-netbsd.h b/os/os-netbsd.h
index 7f5f484..e03866d 100644
--- a/os/os-netbsd.h
+++ b/os/os-netbsd.h
@@ -3,6 +3,7 @@
#include <errno.h>
#include <sys/param.h>
+#include <sys/thr.h>
/* XXX hack to avoid confilcts between rbtree.h and <sys/rb.h> */
#define rb_node _rb_node
#include <sys/sysctl.h>
--
Jens Axboe
next prev parent reply other threads:[~2011-07-30 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 9:43 [PATCH] Use pthread_self instead of thr_self on BSD Bruce Cran
2011-07-30 10:55 ` Jens Axboe
2011-07-30 11:17 ` Bruce Cran
2011-07-30 11:23 ` Jens Axboe [this message]
2011-07-30 12:36 ` Bruce Cran
2011-07-30 12:57 ` Jens Axboe
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=4E33E9C8.1060209@kernel.dk \
--to=axboe@kernel.dk \
--cc=bruce@cran.org.uk \
--cc=fio@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.