In message <[EMAIL PROTECTED]> "Daniel
J. O'Connor" writes:
: You can get an adapter (infact I have one :) which turns a compact flash card
: into a PCMCIA card.. It appears as an ATA HD. I *think* its possible for
: FreeBSD to talk to it, but I haven't tried.
There are patches that originated wi
In message <[EMAIL PROTECTED]> "John W. DeBoskey" writes:
:Basically, it appears to be a combination of PCMCIA-ATA
: support melded together with USB.
:
:Does anyone have any experience with this unit? Am I correct
: that with USB support coming onboard in -current that it would
: be feas
On Mon, 27 Dec 1999, Richard Seaman, Jr. wrote:
> On Mon, Dec 27, 1999 at 10:30:54AM -0800, Kip Macy wrote:
> > They may be preemptive, but I saw a lot of instances with Lyris where one
> > thread could easily monopolize processor time at the expense of all
> > others and I had to add sleeps in a
I have not played with it for several months, so this may no longer be the
case.
-Kip
> Is this recently, or a while ago? FreeBSD user threads used to use
> SIGVTALRM for its pre-emption signal. This didn't count time in
> syscalls. So, if you had a syscall (e
On Mon, Dec 27, 1999 at 10:30:54AM -0800, Kip Macy wrote:
> They may be preemptive, but I saw a lot of instances with Lyris where one
> thread could easily monopolize processor time at the expense of all
> others and I had to add sleeps in at places.
Is this recently, or a while ago? FreeBSD use
They may be preemptive, but I saw a lot of instances with Lyris where one
thread could easily monopolize processor time at the expense of all
others and I had to add sleeps in at places.
>
> FreeBSD user threads have fairly high context switch overhead, especially
> when there are open fds that
On Mon, Dec 27, 1999 at 09:34:49AM -0800, Kip Macy wrote:
> The words "POSIX threads" only describes the API. It says nothing about
> the implementation. On FreeBSD they are non-preemptive user level threads
> (your main was never yielding so the thread you launched did not get any
> time).
Actu
The words "POSIX threads" only describes the API. It says nothing about
the implementation. On FreeBSD they are non-preemptive user level threads
(your main was never yielding so the thread you launched did not get any
time). On Linux they are processes sharing the same virtual memory space,
and a
Hello,
thanks for all your help on my previous posting. Meanwhile my
thread-test works as I followed your instructions and included
a sleep() call.
But on experimenting on this topic I exchanged the sleep() call
with a "while(1);" and had to see that the programm doesn't work
any more.
Why?
I th
In article <[EMAIL PROTECTED]> you write:
>On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote:
>
> > > Hmm, last time I checked, they were just 'serial ports'.
> >
> > Nope. The significance is determined by the software, and you're stuck
> > with the fact that the first serial port is
thanks, I will.
At 07:59 PM 12/23/99 +0100, Wilko Bulte wrote:
>On Thu, Dec 23, 1999 at 07:32:47AM -0800, Kris Kennaway wrote:
>> On Thu, 23 Dec 1999, Stefan Parvu wrote:
>>
>> > Does anybody know real procedures, steps whatever to keep a small an
>> > efficient kernel ?
>>
>> Don't include t
11 matches
Mail list logo
