| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1468.1 | There isn't one, at the moment. | WTFN::SCALES | Despair is appropriate and inevitable. | Wed Jan 22 1997 16:16 | 18 |
| 1468.2 | looks like a hole | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Wed Jan 22 1997 18:04 | 10 |
| 1468.3 | Not a hole, a portable way of doing something non-portable. | WTFN::SCALES | Despair is appropriate and inevitable. | Thu Jan 23 1997 13:49 | 19 |
| 1468.4 | Related issues, but TWO distinct issues | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Thu Jan 23 1997 16:33 | 15 |
| 1468.5 | One issue: portable interfaces for non-portable functions | WTFN::SCALES | Despair is appropriate and inevitable. | Fri Jan 24 1997 10:59 | 23 |
| At the risk of putting in one too many replies... :-)
The basic fact is that stack usage is platform-specific. Thus, specifying
stack sizes must be done in a platform-specific fashion. Thus, you are going
to have platform-specific code if you try to set the stack size explicitly
(unless the trick of doing do in terms of the default size is sufficient).
Therefore, it doesn't matter that there is no portable way of getting the
maximum size. (In point of fact, I expect that the overwhelming majority of
vendors will not impose an explicit maximum -- they will do like we do and
_try_ to create what you ask for, and if there's "room" you'll get it...)
As for the "minimum stack size", I believe that limit is only imposed on
user-allocated stacks (provided via the "stackaddr" attribute). That minimum
doesn't specifically apply to normally created thread stacks. (BTW, don't
use the "stackaddr" attribute...talk about non-portable! It's an
abomination...but I won't go into that here.)
So, I assert that it's all the same issue. There are various cases were
POSIX provides portable interfaces which cannot be used in a portable manner.
Webb
|
| 1468.6 | | SMURF::DENHAM | Digital UNIX Kernel | Fri Jan 24 1997 17:13 | 4 |
| Just as a tangent -- Solaris threads probably don't worry too much
about stack sizes becaue they can dynamically grow their stacks.
We can't until the Steel release. So we can't be as sloppy
as they can until then.
|