Displaying 10 results from an estimated 10 matches for "thread_num".
Did you mean:
thread_name
2015 Oct 07
2
[PATCH 0/2] New APIs: set-identifier, get-identifier
This is very useful for debugging multithreaded programs.
Rich.
2014 Jun 26
2
About memory index/search in multithread program
There may be some solutions?for example
class XAPIAN
{
*static* int InitDatabase(); //for reading only, do not need lock, but
if writing use lock
int Search(); //safe in one object, do not need lock
};
XIPIAN xp[ THREAD_NUM ];
one thread use one object, they use one database.
these can be in memory with one database.
2014-06-24 20:48 GMT+08:00 Olly Betts <olly at survex.com>:
> On Thu, Jun 19, 2014 at 10:52:13PM +0800, Yanxiong Lu wrote:
> > Why xapian don't support memory index/search ?
> &...
2014 Jun 19
2
About memory index/search in multithread program
hi,
Why xapian don't support memory index/search ?
I know there is a method can create memory datebase, like this:
Xapian::WritableDatabase db(Xapian::InMemory::open());
*But, if i use these in multithread program, i need create many
datebases!!*
Xapian::WritableDatabase db1(Xapian::InMemory::open()); //used in thread1
Xapian::WritableDatabase db2(Xapian::InMemory::open()); //used in
2012 Feb 15
2
[PATCH 0/2] Make appliance building thread-safe (RHBZ#790721).
These two patches make appliance building thread-safe. The first adds
a test which easily demonstrates the problem. The second fixes the
issue.
For more information see Ian McLeod's analysis of the bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=790528#c5
Rich.
2016 Mar 06
8
[PATCH 0/5] Use less stack.
Various changes/fixes to use smaller stack frames.
Rich.
2016 Sep 08
4
[PATCH 0/3] Use gnulib's getprogname
Hi,
this series update libguestfs to a recent gnulib version, so that we
can use its new getprogname module, and solve altogether one of the
porting issues (the need for 'program_name' by the error module of
gnulib), and have a single way to get the name of the current program.
A number of changes in tools mostly, although mechanical.
Thanks,
Pino Toscano (3):
Update gnulib to latest
2016 Mar 07
2
[PATCH v2] Use less stack.
...nr_threads];
+ thread_data = malloc (sizeof (struct thread_data) * nr_threads);
+ threads = malloc (sizeof (pthread_t) * nr_threads);
+ if (thread_data == NULL || threads == NULL)
+ error (EXIT_FAILURE, errno, "malloc");
for (i = 0; i < nr_threads; ++i) {
thread_data[i].thread_num = i;
diff --git a/erlang/erl-guestfs-proto.c b/erlang/erl-guestfs-proto.c
index 658a0ef..0c2f545 100644
--- a/erlang/erl-guestfs-proto.c
+++ b/erlang/erl-guestfs-proto.c
@@ -201,11 +201,14 @@ ETERM *
make_string_list (char **r)
{
size_t i, size;
+ ETERM **t;
for (size = 0; r[size] != NUL...
2016 Apr 04
0
[PATCH 2/2] Use 'error' function for fprintf followed by exit.
...XIT_FAILURE);
- }
+ if (optind != argc)
+ error (EXIT_FAILURE, 0,
+ "extra arguments found on the command line");
/* Calculate the number of threads to use. */
if (P > 0)
@@ -205,11 +194,8 @@ run_test (size_t P)
for (i = 0; i < P; ++i) {
thread_data[i].thread_num = i;
err = pthread_create (&threads[i], NULL, start_thread, &thread_data[i]);
- if (err != 0) {
- fprintf (stderr, "%s: pthread_create[%zu]: %s\n",
- guestfs_int_program_name, i, strerror (err));
- exit (EXIT_FAILURE);
- }
+ if (err != 0)
+...
2015 Feb 14
2
[PATCH 0/2] Change guestfs__*
libguestfs has used double and triple underscores in identifiers.
These aren't valid for global names in C++.
(http://stackoverflow.com/a/228797)
These large but completely mechanical patches change the illegal
identifiers to legal ones.
Rich.
2016 Apr 04
2
[PATCH 1/2] Use 'error' function consistently throughout.
Wherever we had code which did:
if (something_bad) {
perror (...);
exit (EXIT_FAILURE);
}
replace this with use of the error(3) function:
if (something_bad)
error (EXIT_FAILURE, errno, ...);
The error(3) function is supplied by glibc, or by gnulib on platforms
which don't have it, and is much more flexible than perror(3). Since
we already use error(3), there seems to be