> On Sep 26, 2017, at 8:35 PM, Toke Høiland-Jørgensen
> <[email protected]> wrote:
>
> Pete Heist <[email protected]> writes:
>
> > Yes, because the seqno is just the array index. I’ll add the seqno
> > explicitly to make it easier to consume.
>
> So what happens if a packet is lost? There'll be an empty element in the
> array? That's... unusual... ;)
An element in the array with an empty receive timestamp (which I could rather
make 0 timestamps). As it stands now:
{
"client": {
"receive": {},
"send": {
"wall": 1506452529563882735,
"monotonic": 2006485513
}
},
"server": {
"receive": {},
"send": {}
}
}
But yeah, seqno should be there for ease / clarity.
> Well, whether they are omitted or can be blank, it'll be important to
> know what to expect :)
Indeed. :)
> > Adding the JSON encoder was a relative “whopper” at around 250K
> > unstripped (also eyeballed). If I’m looking for somewhere to cut, I
> > could later find another encoder or just write JSON by hand. I did
> > some gyrations to avoid pulling in regexp in a couple of cases. :)
>
> Huh, that's quite impressive (and not in a good way). But then it
> probably can't run on the tiniest of devices anyway since there's no
> MIPS support in Go (last I looked anyway)…
There is 32-bit MIPS support as of Go 1.8 (2/2017), BUT, and just found out
this is a big but:
"Go now supports 32-bit MIPS on Linux for both big-endian (linux/mips) and
little-endian machines (linux/mipsle) that implement the MIPS32r1 instruction
set with FPU or kernel FPU emulation. Note that many common MIPS-based routers
lack an FPU and have firmware that doesn't enable kernel FPU emulation; Go
won't run on such machines."
I just tried compiling a really tough program:
func main() {
fmt.Println("Hello MIPS!")
}
tron:~/src/github.com/peteheist/irtt:% GOOS=linux GOARCH=mipsle go build
-ldflags="-s -w" ./cmd/hellomips
ran it on an OM2P-HS and got this:
root@Service_West:/tmp# ./hellomips
./hellomips: line 1: syntax error: unexpected “("
That’s a disappointment, as I’d been under the assumption it was going to work
and I could use IRTT on these devices. But, I can still test _through_ them
with other devices.
Does LEDE have FPU emulation enabled? I’ll try to find out more!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/106#issuecomment-332308580_______________________________________________
Flent-users mailing list
[email protected]
http://flent.org/mailman/listinfo/flent-users_flent.org
