Re: Line-oriented blocking input from sockets?

2003-07-16 Thread Matthew Mondor
On Mon, Jul 14, 2003 at 01:09:15PM -0700, Damon Hastings wrote: > Hey, that's great! I was a little concerned for a moment there. But with > it just swapping a few pointers each context switch, Pth should be much > faster than Linux Pthreads. (And I have 1GB physical RAM, so no worries > about

Re: Line-oriented blocking input from sockets?

2003-07-16 Thread Matthew Mondor
On Mon, Jul 14, 2003 at 07:58:11PM +0200, Ralf S. Engelschall wrote: > In Pth only the (original) stack of the main thread is auto-growing > (done by the OS), while the other stacks are fixed size stacks. If you > don't have very high recursion levels or other functions uses large > buffers on the

pth_malloc()/pth_realloc()/pth_free()

2003-07-16 Thread Matthew Mondor
Hi, Has there ever been a plan to eventually include memory allocation primitives as part of the PTh library to minimize the frequency of calls to malloc()/free()? The reason why I am wondering is that kernels will often cause a process to sleep for an undetermined amount of time if memory resour

Re: Line-oriented blocking input from sockets?

2003-07-16 Thread Matthew Mondor
On Fri, Jul 11, 2003 at 03:04:18PM -0700, Damon Hastings wrote: > This is probably a stupid question, but how do you do line-oriented blocking > socket reads in Pth? There's a pth_read() which I assume blocks until a > specified number of bytes (or eof) are received -- but I'm looking for > somet

Re: PTH is broke or I don't understand threads.

2003-04-01 Thread Matthew Mondor
On Tue, Apr 01, 2003 at 12:15:44PM -0800, Steve Alstrin wrote: > I compiled the test program, included with distro, and it appears that no > thread will start until a join is done on it. When I compile the test > program "test_pthread" with native threads the threads start after the > pthread_crea

Message size and data fields

2002-11-12 Thread Matthew Mondor
Hi again, In the following bit of code, I set the message size field of a message. If they are internally moved among ports by only relinking the message node, is this size relevant? I'm sure it would be if we had message allocation and/or pool management backend for them, but we allocate them our

Re: pth_uctx_* (was: Re: pth_msgport_create() and pth_mctx_*())

2002-11-07 Thread Matthew Mondor
On Sun, Nov 03, 2002 at 11:02:53AM +0100, Ralf S. Engelschall wrote: > On Thu, Oct 24, 2002, Matthew Mondor wrote: > > > > > Yes, that is also why I suggest to perhaps provide an SVR4/SUS like > > interface, which could consist of C functions... and then exported and &g

Re: pth_msgport_create() and pth_mctx_*()

2002-10-24 Thread Matthew Mondor
On Wed, 23 Oct 2002 15:58:40 +0200 "Ralf S. Engelschall" <[EMAIL PROTECTED]> wrote: > Good idea. The name for pth_msgport_create() is actually only required > of one wants to search the message port via pth_msgport_find(). So I've > changed this now for GNU Pth 1.5.0 to allow a NULL name, too. Tha

Re: netbsd and pth threads

2002-10-24 Thread Matthew Mondor
On Tue, 22 Oct 2002 16:11:24 -0500 Jeff Rhine <[EMAIL PROTECTED]> wrote: > Trying to compile ntop with netbsd 1.5.x and pth for provide threads > support ? You tried using the binary package netbsd provides, or pkgsrc? Note that also pth is provided, which compiles by default with POSIX thread wr

pth_msgport_create() and pth_mctx_*()

2002-10-22 Thread Matthew Mondor
I really enjoy Pth, and am using it's functions quite extensively in my mmftpd and mmmail servers (http://mmondor.gobot.ca/software.html or cvs -z9 -d:pserver:[EMAIL PROTECTED]/cvsroot co mmsoftware). I especially like it's event handling, which even POSIX threads don't provide. Here are notes of i