All of lore.kernel.org
 help / color / mirror / Atom feed
* [parisc-linux] nanosleep
@ 2002-11-08 11:16 Berthold Gunreben
  2002-11-08 16:12 ` Carlos O'Donell
  0 siblings, 1 reply; 4+ messages in thread
From: Berthold Gunreben @ 2002-11-08 11:16 UTC (permalink / raw)
  To: parisc-linux

Hi List,    
    
I tried to compile glibc2.3.1, and have some problems with the threading support there.     
When using perl with the new glibc on a C240, things seem to work without problems. On    
a 715/33, I get (probably) endless loops with lots of sched_yield() calls.    
    
In the Internet, I found the following site:    
http://sources.redhat.com/ml/libc-alpha/2000-02/msg00057.html   
where Andrea Arcangeli fixed a kernel problem with nanosleep on kernel 2.2 and 2.3, and  
also provided a testprogram. Here are the results of my test:  
  
C240: (2.4.19-pa20)  
# ./nanotest & sleep 4; killall nanotest  
[1] 8455  
userspace             15 sec 778496030 nsec  
kernel                15 sec 800000000 nsec  
[1]+  Done                    ./nanotest  
  
715/33: (2.4.17-32)  
# ./nanotest & sleep 4; killall nanotest  
[1] 1840  
userspace             15 sec 422651030 nsec  
kernel                15 sec 450000000 nsec  
[1]+  Done                    ./nanotest  
  
Intel based for reference: (2.4.19)  
# ./nanotest & sleep 4 ; killall nanotest  
[1] 19648  
userspace             15 sec 984455030 nsec  
kernel                15 sec 984477030 nsec  
[1]+  Done                    ./nanotest  
  
Is there a bugfix missing for parisc? 
 
Berthold 
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! 
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] nanosleep
  2002-11-08 11:16 [parisc-linux] nanosleep Berthold Gunreben
@ 2002-11-08 16:12 ` Carlos O'Donell
  2002-11-09  8:32   ` b.gunreben
  0 siblings, 1 reply; 4+ messages in thread
From: Carlos O'Donell @ 2002-11-08 16:12 UTC (permalink / raw)
  To: Berthold Gunreben; +Cc: parisc-linux

> Hi List,         
> I tried to compile glibc2.3.1, and have some problems with the threading support there.     
> When using perl with the new glibc on a C240, things seem to work without problems. On    
> a 715/33, I get (probably) endless loops with lots of sched_yield() calls.    
     
glibc 2.3.1 from debian CVS or upstream?

c.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] nanosleep
  2002-11-08 16:12 ` Carlos O'Donell
@ 2002-11-09  8:32   ` b.gunreben
  2002-11-09 19:26     ` Carlos O'Donell
  0 siblings, 1 reply; 4+ messages in thread
From: b.gunreben @ 2002-11-09  8:32 UTC (permalink / raw)
  To: parisc-linux

Carlos O'Donell wrote:
> 
> > Hi List,
> > I tried to compile glibc2.3.1, and have some problems with the threading support there.
> > When using perl with the new glibc on a C240, things seem to work without problems. On
> > a 715/33, I get (probably) endless loops with lots of sched_yield() calls.
> 
> glibc 2.3.1 from debian CVS or upstream?

This is upstream with hppa patches from the debian tree. 

The report was probably bad. In the mail thread I mentioned in my
previous mail, the nanosleep in the kernel was fixed because of
threading problems. If I understand it correctly, threading will always
have problems without a realy working nanosleep.

Berthold

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [parisc-linux] nanosleep
  2002-11-09  8:32   ` b.gunreben
@ 2002-11-09 19:26     ` Carlos O'Donell
  0 siblings, 0 replies; 4+ messages in thread
From: Carlos O'Donell @ 2002-11-09 19:26 UTC (permalink / raw)
  To: b.gunreben; +Cc: parisc-linux

> > glibc 2.3.1 from debian CVS or upstream?
> 
> This is upstream with hppa patches from the debian tree. 

That's currently broke, and I've been slotting in my time to fix this.
Currently rebuilding glibc :}
 
> The report was probably bad. In the mail thread I mentioned in my
> previous mail, the nanosleep in the kernel was fixed because of
> threading problems. If I understand it correctly, threading will always
> have problems without a realy working nanosleep.
 
Yes. You'll see it's use sprinkled in linuxthreads/* and in particular 
spinlock.c

c.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-11-09 19:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-08 11:16 [parisc-linux] nanosleep Berthold Gunreben
2002-11-08 16:12 ` Carlos O'Donell
2002-11-09  8:32   ` b.gunreben
2002-11-09 19:26     ` Carlos O'Donell

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.