[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [Nicolai Hanssing <nuh@kampsax.dtu.dk>] (fwd)



>From owner-rtl Wed Jun 27 06:26:59 2001
Received: from eising.k-net.dk (eising.k-net.dtu.dk [130.225.71.229])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f5RCQwe15969
	for <rtl@fsmlabs.com>; Wed, 27 Jun 2001 06:26:58 -0600
Received: from carlsberg.kampsax.dtu.dk (carlsberg.kampsax.dtu.dk [192.38.212.2])
	by eising.k-net.dk (Postfix) with SMTP id 48B2BC08A
	for <rtl@fsmlabs.com>; Wed, 27 Jun 2001 14:20:42 +0200 (CEST)
Received: (qmail 17268 invoked from network); 27 Jun 2001 12:20:42 -0000
Received: from carlsberg.kampsax.dtu.dk (HELO carlsberg) (nuh@192.38.212.2)
  by carlsberg.kampsax.dtu.dk with SMTP; 27 Jun 2001 12:20:42 -0000
Date: Wed, 27 Jun 2001 14:20:42 +0200 (CEST)
From: Nicolai Hanssing <nuh@kampsax.dtu.dk>
To: rtl@fsmlabs.com
Subject: Newbieproblems - stacksize
In-Reply-To: <20010626131802.A8050@fsmlabs.com>
Message-ID: <Pine.LNX.4.21.0106271405050.14394-100000@carlsberg.kampsax.dtu.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dear Listmembers

First of a simple question most of you can propably answer:

* Is operations on the fifos "atomic"? 
	Both in userspace and in the rtkernel?

* Where can I find SSIZE_MAX [MAX bytesize for read()/write()] on an i3x86
2.2.18/19?

* What is the max size of an fifo-queue?
	And unless it fails on initialisation there was enough
kernelmemory - right?

* Are there an "RTL_SSIZEMAX" for operations on the rtl_fifos?

For some reason if havent been able to find any place in the manpages that
 states that the RTFIFOs are Atomic, though the fifos work as if they were
...

--

Next up is a problem with a simpel POSIX_thread:

For some reason my thread keep chrashing the system [both in
2.2.18-rtlv3.0 and 2.2.19-rtlv3.1pre3]. I've been looking over the code
throughly, and it seems allright. There's no dynamic memoryallocation, and
only some simple IO to hardcoded adresses. I.e. it shouldnt chrash due to
pointer-error or memory-leaks.
However the thread uses some quite large variables, that according to my
memmory are allocated on the stack (?). 

How can I tell if the stack runs out [has run out - overwrite kernelspace 
- whatever], and how can I increase the size
dynammicly?

--

Hmm, maybe I should have spilt the mail i two - nahh I'll send you some
other questions instead :-)

Regards
	Nicolai Hanssing

----- End of forwarded message from owner-rtl@fsmlabs.com -----