Hi,
The code below is compiled with -fopenmp and run on FreeBSD6/7 (i386, amd64):
#include
#include
int n = 4, m = 2;
int main () {
for (;;) {
int i;
//sleep(2);
#pragma omp parallel for num_threads(m)
for(i = 0; i < 1; i++) {}
On Monday 11 May 2009 2:27:48 pm j...@0xabadba.be wrote:
> John,
>
> Thank you for your input on this matter, I'm excited to write
> some software for this project since its given me great code to learn
> from as i've grown up (still a kid though :). My questions are a bit
> more detailed be
On Monday 11 May 2009 2:58:14 pm Kostik Belousov wrote:
> On Mon, May 11, 2009 at 02:46:14PM -0400, John Baldwin wrote:
> > On Monday 11 May 2009 2:33:09 pm Kostik Belousov wrote:
> > > On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
> > > > On Friday 28 September 2007 10:39:56 pm Igh
On Mon, May 11, 2009 at 02:46:14PM -0400, John Baldwin wrote:
> On Monday 11 May 2009 2:33:09 pm Kostik Belousov wrote:
> > On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
> > > On Friday 28 September 2007 10:39:56 pm Ighighi wrote:
> > ^
>
> Yes, I had th
On Monday 11 May 2009 2:33:09 pm Kostik Belousov wrote:
> On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
> > On Friday 28 September 2007 10:39:56 pm Ighighi wrote:
> ^
Yes, I had this stuck in the back of my head from when it first appeared.
> > > The PO
On Mon, May 11, 2009 at 02:05:07PM -0400, John Baldwin wrote:
> On Friday 28 September 2007 10:39:56 pm Ighighi wrote:
^
> > The POXIX prototype for readlink(2) is:
> > ssize_t readlink(const char *restrict path, char *restrict buf, size_t
> > bufsize);
>
> It can't si
John,
Thank you for your input on this matter, I'm excited to write
some software for this project since its given me great code to learn
from as i've grown up (still a kid though :). My questions are a bit
more detailed below.
On Mon, May 11, 2009 at 12:24 PM, John Baldwin wrote:
> On Fri
On Friday 28 September 2007 10:39:56 pm Ighighi wrote:
> The POXIX prototype for readlink(2) is:
> ssize_t readlink(const char *restrict path, char *restrict buf, size_t
> bufsize);
It can't simply be corrected as it would change the ABI and thus requires a
new system call, etc. However, do you
On Friday 08 May 2009 5:41:17 pm Ed Schouten wrote:
> A solution would be to solve it as follows:
>
> - Use a semaphore, initialized to some insane high value to put an upper
> limit on the amount of concurrent sysctl calls. I'm not sure whether
> this is really needed. Maybe this issue is not
2009/5/8 Ryan Stone :
> Your kernel thread likely has a higher priority than userspace threads.
>
> Ryan Stone
>
Thanks for your reply Ryan.
So that I understand this correctly, if I had two kernel threads, one
with a high priority, and one with a low priority, and both are
PRI_TIMESHARE, then th
10 matches
Mail list logo
