lguest/plan9 isn't terribly efficient
at minimising the context switching that happens when packets are sent
and received.
-rod
n server: 1.2 seconds
plan9 in lguest on the same server : 2.2 seconds
Oldish labs kernels in both cases.
-rod
ted me on the usb
drivers, but I very nearly finished a driver for the sdcard, and
got some way with a flash driver, which would have been useful to
update the kernel from within plan9. It is all based on the bitsy
code, so is probably some way out of line with the current
arm developments.
-rod
7;s obviously there for a reason. I
know it's probably obsolete stuff, but it seems a shame if old bits
just crumble through natural wastage. Can anyone shed any light?
-rod
ed and
the block was declared "clean" but was grabbed by the unlink thread.
The flush thread now can't reacquire the block lock on return from
vtSleep(b->ioready).
Does this sound feasible? Even if so, I'm not sure how to fix it.
- rod
Further notes:
Probably not relate
ip addresses manage to respond with a syn before
one of them is is "chosen". The other five are reset. I'm finding it
hard to convince myself that this is good behaviour.
Rod
a host that has multiple ip addresses and none of
them respond then errstr is set to "progname pid: alarm".
This doesn't seem consistent. Would it be possible to have "connection
refused" set in the second case too? I think both scenarios are
essentially the same as far as client code is concerned.
Rod
s installed and ran fine.
Interestingly, I had another laptop of the same model (inspiron 3500)
which also failed identically.
I concluded that there was most likely something about the timing in
the ata driver that tickled the drive/interface combination.
Rod
isn't
necessarily the case, leading to bad things.
in db.c:
60a61
> int r;
64c65,66
< return strcmp(ea->name, eb->name);
---
> r = strcmp(ea->name, eb->name);
> return r > 0 ? 1 : r < 0 ? -1 : 0;
Rod
;-
PS. Subsequently I
>presents both an input endpoint #2 and an output endpoint #2
Ah, thanks. I wasn't aware that 2 endpoints could have the same number
and be distinct only in their data direction. All of the 20 or so
different "sticks" on my desk have separate endpoint numbers.
rod
e with, an endpoint
descriptor (Ed). "newed" is called for each Qio to link the Qio's
endpoint descriptor into the controller's chain.
I can't figure out why there are two Qio structs. The usb spec says
that bulk/interrupt endpoints are unidirectional, so why wouldn't just
a single one do?
Thanks,
rod
e sequence won't affect anything.
rod
n even when interrupts
are disabled by the ilock?
Thanks for any insight.
rod
>a plan 9 client normally re-used fids,
Ah right, thank you - I see that now. I have just tried native plan9
and, of course, it works fine. I was running 9vx earlier and it
seems as if the fid increments each time.
Rod
riginally had 16 bit fids? If
so, it suggests that no-one has used kfs in anger for a while.
Rod
there's currently a picture at this
location:
http://server.hemiola.co.uk/zaurus.pdf
Rod
16 matches
Mail list logo
