Re: [eigen] ThreadSafety of Eigen? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] ThreadSafety of Eigen?
- From: Björn Piltz <bjornpiltz@xxxxxxxxxxxxxx>
- Date: Wed, 31 Mar 2010 18:02:29 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=X2Qkpje0IQjyCd9dxdoC18HSLwBqfzXnrX6Ht/hj3nQ=; b=SHg3IrM1MBIiQW/ly6O1Zsckazu8Tq+ySnWd/H4c9suDr0J4mRBzrXFXHD5k0tKs0P 90cUW2Zws0hS30kG0aTXcwzxonK27ULh+IwxHliy1AuiBi/J21dnU2aeWoGOVT4+emUx C9EgxzWsI0+mpxk19fqxGEJWmEBH4Qw2E9nvM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=IbNOYps8OWMN7muhnFDS1JnHM1cKZi6BfDKZLfpGXJEs6lQlbzA+2wd2cL326wNPRi CeG+2nILSLpLNupnOB1XQ5ybupyM64MxUv9cJyIAnvBeXFGR+dwoXY4OE48vcvqThGV6 Ff0DMK2A459kNfYBvntjDLk6a3keEYaT5653U=
> By thread-safe we mean what i described in my first email: if
> you have two matrices m1 and m2, then you can have thread1 working on
> m1 and thread2 working on m2 without any interference.
>
> By re-entrant we mean that the same function can be called
> concurrently by 2 threads.
I think that should be the otherway around.
Here is how Qt defines it(Not that it matters, since we are on the
same page on which kind ot thread safety Eigen should provide):
reentrant - Describes a function which can be called simultaneously by
multiple threads when each invocation of the function references
unique data. Calling a reentrant function simultaneously with the same
data is not safe, and such invocations should be serialized.
thread-safe - Describes a function which can be called simultaneously
by multiple threads when each invocation references shared data.
Calling a thread-safe function simultaneously with the same data is
safe, since all access to the shared data are serialized.