I am running FreeBSD 4.0-RELEASE on x86 with gcc 2.95.2 and the
httperf-0.6 port gives a SIGFPE and dumps core when run against a system
that has no web server running. (The default behavior is to measure
localhost when no arguments are specified).
It seems this is caused by a divide by zero er
> From [EMAIL PROTECTED] Tue Apr 25 06:02:09 2000
> Date: Tue, 25 Apr 2000 05:23:39 +0300
> From: A G F Keahan <[EMAIL PROTECTED]>
> To: "Richard Seaman, Jr." <[EMAIL PROTECTED]>
> Cc: Jason Evans <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: Multithreaded server performance
>
> Jason and
Hi All-
I want to be a part of your team and do something for freeBSD. Could
somebody tell me how to start?
Thanks a lot.
Best Regards,
Dehui Peng
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
See RFC1122, section 3.2.1.3, available at
http://www.cis.ohio-state.edu/htbin/rfc/rfc1122.html
http://www.faqs.org/rfcs/rfc1122.html
> On Fri, Mar 31, 2000 at 12:57:40PM +0100, Nik Clayton wrote:
[...]
> > I thought that 127/8 was the "local net", and that packets sent to any of
> > those a
On Mon, Apr 24, 2000 at 09:58:49PM -0500, Chris Costello wrote:
> On Monday, April 24, 2000, Brian O'Shea wrote:
> > Yea, I took a look at lib/libc_r/uthread/uthread_read.c too, but it
> > didn't paint the whole picture for me. Specifically, I couldn't find
> > the definition for the _thread_sys_
On Mon, Apr 24, 2000 at 05:07:00PM -0500, Chris Costello wrote:
>FreeBSD's threads implement has its own read() function which
> will make a non-blocking read() call (using the _real_ syscall)
> for the specified amount of bytes. Now a non-blocking read()
> call fails unless all the data in n
On Monday, April 24, 2000, Brian O'Shea wrote:
> Yea, I took a look at lib/libc_r/uthread/uthread_read.c too, but it
> didn't paint the whole picture for me. Specifically, I couldn't find
> the definition for the _thread_sys_read() function. It looks like the
> polling magic to which Jason Evans
Hello,
I would like to suggest to read the following articles
at http://www.cs.wustl.edu/~schmidt/report-doc.html
(he has there a ps doc for each article)
13.Comparing Alternative Programming Techniques for Multi-threaded Servers --
the Thread-per-Session Concurren
I received the following from SUN Microsystems:
---Susan Grabau <[EMAIL PROTECTED]>
Thanks for your note. Here's a bit of an update.
We are planning on making the StarOffice source code available in the
next few months. This will enable OS/2 users and organizations to
migr
Jason and Richard,
thank you very much for your explanations of libc_r and
LinuxThreads. Due to the significant processing time of each request
(typically between 50-800ms, averaging 100ms), I doubt that FreeBSD's
threads would perform any worse than if I forked a separate proce
Now that the 4.0 branch split is well behind us, would someone with
commit privs mind taking a look at the kern/15251? Thanks,
Kelly
--
Kelly Yancey - [EMAIL PROTECTED] - Belmont, CA
System Administrator, eGroups.com http://www.egroups.com/
Maintainer, BSD Driver Databa
> Linux runs into problems at less than 4000 threads because of a limit on
> the total number of processes, even if the thread stack size is decreased.
I believe this restriction was eliminated in the 2.2.x series.
-MB
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
On Mon, Apr 24, 2000 at 02:11:11PM -0700, Jason Evans wrote:
> > Could you elaborate? The text that I am using [1] warns about blocking
> > system calls putting the process (and thus all user threads) to sleep.
> > This book has no FreeBSD specific information, so anything specific to
> > FreeBSD
On Mon, Apr 24, 2000 at 04:44:05PM -0500, Richard Seaman, Jr. wrote:
> On Sun, Apr 23, 2000 at 09:21:15PM -0700, Jason Evans wrote:
> > FreeBSD's threads should perform adequately given the design of your program
> > and the hardware you listed. Actually trying it on the various operating
> > sys
On Monday, April 24, 2000, Brian O'Shea wrote:
> On Mon, Apr 24, 2000 at 06:13:53AM -0400, Daniel Eischen wrote:
> > On Mon, 24 Apr 2000, Brian O'Shea wrote:
> > >
> > > I was under the impression that, because user thread scheduling is done
> > > in user mode, a thread that goes to sleep calling
On Sun, Apr 23, 2000 at 09:21:15PM -0700, Jason Evans wrote:
> On Mon, Apr 24, 2000 at 05:17:10AM +0300, A G F Keahan wrote:
> > I am currently porting a multithreaded TCP server from NT (yech!) to
> > UNIX using pthreads. The server has a fairly straightforward design --
> > it opens a thread fo
On Mon, Apr 24, 2000 at 06:13:53AM -0400, Daniel Eischen wrote:
> On Mon, 24 Apr 2000, Brian O'Shea wrote:
> >
> > I was under the impression that, because user thread scheduling is done
> > in user mode, a thread that goes to sleep calling a blocking read()
> > system call will put the entire pr
George Cox wrote:
>
> On 24/04 00:08, Christian Weisgerber wrote:
>
> > Hasn't O'Brien recently said that in fact "-pipe" is already the default
> > for our cc, so explicitly specifying the option doesn't do anything?
>
> Try compiling a 'hello world' program with and without the '-pipe' opti
On 24/04 00:08, Christian Weisgerber wrote:
> Hasn't O'Brien recently said that in fact "-pipe" is already the default
> for our cc, so explicitly specifying the option doesn't do anything?
Try compiling a 'hello world' program with and without the '-pipe' option
but with '-v' switched on in bot
-On [2420 20:02], Arun Sharma ([EMAIL PROTECTED]) wrote:
>Comments ?
>
>$ cat test.c
>#include
>#include
>$ cc -D_POSIX_SOURCE -c test.c
>In file included from test.c:2:
>/usr/include/sys/socket.h:47: syntax error before `sa_family_t'
>/usr/include/sys/socket.h:47: warning: data definition h
Brian Fundakowski Feldman wrote:
> On Mon, 24 Apr 2000, Ben Smithurst wrote:
>
>> why allow csh in the Makefile when the setting of DEFSHELL it results in
>> will not compile? Have I missed something?
>
> It's there to allow you attempt to shoot yourself in the foot more safely.
> Too much sho
Dear folks
Recently, I have notice a problem.
When I send or receive data blocks <= 4096 with READ or WRITE system calls,
everything work well, when I increase the block size, syscalls return the
correct value but the network throughput falls down %80.
I have increased the socket rcv/snd buffer s
On Mon, 24 Apr 2000, Roman N. Dmitrik wrote:
> We bought IA-300 PCI ADSL Modem( chipsets i901889F/i90135F ITeX)
> and have trouble with installing it in FreeBSD 3.4.
> Does FreeBSD support this device if yes were we can read about this problem ?
No, FreeBSD doesn't support any ADSL chipset. Curr
Hello,
We bought IA-300 PCI ADSL Modem( chipsets i901889F/i90135F ITeX)
and have trouble with installing it in FreeBSD 3.4.
Does FreeBSD support this device if yes were we can read about this problem ?
Please help
--
Regards,
Roman D.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsub
> Speaking of which, I'd really like to see bridge support getting added to
> all new NIC drivers from now on. However, the current bridge interface
> leaves something to be desired...
hopefully things will improve if someone finds the time to
extend ether_input() as suggested by archie Cobbs an
On Mon, 24 Apr 2000, Brian O'Shea wrote:
> On Sun, Apr 23, 2000 at 09:21:15PM -0700, Jason Evans wrote:
> >
> > FreeBSD's libc_r does not use clone() or anything similar. Instead, it is
> > a userland call conversion library that multiplexes threads in a single
> > process. This style of threa
On Mon, 24 Apr 2000, Julian Elischer wrote:
> > Sure. smbfs actually consists of two major parts - SMB requester
> > and filesystem itself. SMB requester handles all protocol details and
> > gives clear interface like 'connect to server', 'connect to share', 'send
> > request' etc. An ope
Boris Popov wrote:
>
> On Mon, 24 Apr 2000, Julian Elischer wrote:
>
> Sure. smbfs actually consists of two major parts - SMB requester
> and filesystem itself. SMB requester handles all protocol details and
> gives clear interface like 'connect to server', 'connect to share', 'send
> r
On Mon, 24 Apr 2000, Julian Elischer wrote:
> > in the near future I'm going to release beta
> > version of native,
> > kernel side SMB/CIFS filesytem for FreeBSD. It uses
> > device /dev/net/nsmbX
> > for the userland <-> kernel interaction. Currently it uses
> > major number
> > assi
Boris Popov wrote:
>
> Hello,
>
> in the near future I'm going to release beta
> version of native,
> kernel side SMB/CIFS filesytem for FreeBSD. It uses
> device /dev/net/nsmbX
> for the userland <-> kernel interaction. Currently it uses
> major number
> assigned to the 'joys
> in the near future I'm going to release beta version of native,
> kernel side SMB/CIFS filesytem for FreeBSD. It uses device /dev/net/nsmbX
You're a committer, just grab an available one. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in
On Sun, Apr 23, 2000 at 09:21:15PM -0700, Jason Evans wrote:
>
> FreeBSD's libc_r does not use clone() or anything similar. Instead, it is
> a userland call conversion library that multiplexes threads in a single
> process. This style of threads library should perform well for the type of
> app
Hello,
in the near future I'm going to release beta version of native,
kernel side SMB/CIFS filesytem for FreeBSD. It uses device /dev/net/nsmbX
for the userland <-> kernel interaction. Currently it uses major number
assigned to the 'joystick' device which can make some peoples un
33 matches
Mail list logo
