Daniel Eischen wrote:
>
> Some of the man pages and cancellation support came from OpenBSD
> (David Leonard). The man page appears to have been written on
> Jan 17, 1999 for OpenBSD. FreeBSD-current and -stable came much
> later.
Ah, that's what I saw. Thanks for the clarification.
--
On Mon, 6 Mar 2000, Wes Peters wrote:
> John Baldwin wrote:
> >
> > On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
> > > [...]
> > >
> > >> What's the reason for locking the file descriptors
> > >> for *all* system calls? especially those I mentioned?
> > >>
> > >> Where is pthread_cancel() ?
> >
John Baldwin wrote:
>
> On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
> > [...]
> >
> >> What's the reason for locking the file descriptors
> >> for *all* system calls? especially those I mentioned?
> >>
> >> Where is pthread_cancel() ?
> >
> > are you using -stable (3.x)? there is no ``pthread_
On Mon, 6 Mar 2000, Yevmenkin, Maksim N, CSCIO wrote:
> [...]
>
> > > are you using -stable (3.x)? there is no ``pthread_cancel''
> > in -stable.
> > > use -current.
> >
> > Bt!!! Wrong!
> >
> > > uname -a
> > FreeBSD server.baldwin.cx 3.4-STABLE FreeBSD 3.4-STABLE #6:
> > Sun Feb 20 20:
[...]
> > are you using -stable (3.x)? there is no ``pthread_cancel''
> in -stable.
> > use -current.
>
> Bt!!! Wrong!
>
> > uname -a
> FreeBSD server.baldwin.cx 3.4-STABLE FreeBSD 3.4-STABLE #6:
> Sun Feb 20 20:24:19 EST 2000
> [EMAIL PROTECTED]:/usr/source/src/sys/compile/SERVER i
On 06-Mar-00 Yevmenkin, Maksim N, CSCIO wrote:
> [...]
>
>> What's the reason for locking the file descriptors
>> for *all* system calls? especially those I mentioned?
>>
>> Where is pthread_cancel() ?
>
> are you using -stable (3.x)? there is no ``pthread_cancel'' in -stable.
> use -current.
Titus von Boxberg wrote:
> Daniel Eischen wrote:
> >
> > > Apparently it is not possible to shutdown those
> > > threads from a third thread, neither using close nor shutdown(2) for
> > > the socket I/O if the threads are blocked during read.
> > >
> > > What methods can one use to unblock such a
[...]
> What's the reason for locking the file descriptors
> for *all* system calls? especially those I mentioned?
>
> Where is pthread_cancel() ?
are you using -stable (3.x)? there is no ``pthread_cancel'' in -stable.
use -current.
or
- use other threads library
- use non-bl
Daniel Eischen wrote:
>
> > Apparently it is not possible to shutdown those
> > threads from a third thread, neither using close nor shutdown(2) for
> > the socket I/O if the threads are blocked during read.
> >
> > What methods can one use to unblock such a blocked-on-read
> > thread?
>
> The c
On Mon, 6 Mar 2000, James FitzGibbon wrote:
> > Some comments? Isn't so?
>
> In my experience, threads are the perfect way to speed up an I/O bound
> application. While one thread is blocked in iowait, others can be
> performing operations that do not contend for the same resource
> (calculatio
* stefan parvu ([EMAIL PROTECTED]) [000306 09:19]:
> I have not so much experience using POSIX threads, but we had in
> university a project and for I/O to use threads is not so good method.
> You slow down the process.
>
> Some comments? Isn't so?
In my experience, threads are the perfect way
> I use two threads to do I/O for a process.
> The I/O takes place either on a socket or
> an I/O device (com port) file descriptor.
>
> Apparently it is not possible to shutdown those
> threads from a third thread, neither using close nor shutdown(2) for
> the socket I/O if the threads are bloc
Hi,
I have not so much experience using POSIX threads, but we had in
university a project and for I/O to use threads is not so good method.
You slow down the process.
Some comments? Isn't so?
stefan
Titus von Boxberg wrote:
>
> Hi,
>
> I use two threads to do I/O for a process.
> The I/O t
13 matches
Mail list logo
