DragonFly users List (threaded) for 2013-03
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Porting sbcl to DragonFly
--20cf3071c9bc5e889004d91d7c6e
Content-Type: text/plain; charset=ISO-8859-1
Hello! I started porting SBCL to DragonFlyBSD. Previous (and only) attempt
was http://leaf.dragonflybsd.org/mailarchive/users/2006-05/msg00108.html as
far as I know. Google gives no more info on "sbcl on dragonfly" except this
link.
So I forked sbcl/sbcl repo from github a while ago and added support for
DragonFly on x86-64 platform (with multithreading support). I even build
stumpwm with sbcl and tried hunchentoot web server. Hunchentoot can handle
100 connections/second. This rate is almost its limit with
one-thread-per-connection model.
Link to repo:
https://github.com/shamazmazum/sbcl-dragonfly
There is a problem nevertheless: use of symbol-value-in-thread in
sb-concurrency tests causes sbcl to crash (not to ldb, but crash
completely!).
So I have some questions:
1. src/runtime/Config.x86-64-freebsd states that we must use 1:1 threading
not m:n threading and uses lthr for that purpose. It seems that there isn't
lthr in dragonfly, only lpthread is present. Should I use it? Is 1:1
threading supported? (It seems to work with lpthread anyway).
2. SBCL uses GCC TLS with (and only with) FreeBSD. I heard something about
lack of "native" TLS in FreeBSD. Is it true? Is TLS present on DragonFly?
3. Can I build and install x86 environment and virtual kernel on x86-64
machine? I prefer not to use VirtualBox if there is possibility to use
vkernel. This is needed to port SBCL to x86 too.
Sorry for possibly stupid questions, I am new both to DragonFlyBSD and SBCL
internals.
Any help of SBCL/Common Lisp hackers would be appreciated. I have really no
idea how to fix sb-concurrency right now.
--20cf3071c9bc5e889004d91d7c6e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div></div>Hello! I started porting SBCL to DragonFly=
BSD. Previous (and only) attempt was <a href=3D"http://leaf.dragonflybsd.or=
g/mailarchive/users/2006-05/msg00108.html">http://leaf.dragonflybsd.org/mai=
larchive/users/2006-05/msg00108.html</a> as far as I know. Google gives no =
more info on "sbcl on dragonfly" except this link.<br>
<br></div><div>So I forked sbcl/sbcl repo from github a while ago and added=
support for DragonFly on x86-64 platform (with multithreading support). I =
even build stumpwm with sbcl and tried hunchentoot web server. Hunchentoot =
can handle 100 connections/second. This rate is almost its limit with one-t=
hread-per-connection model.<br>
<br></div><div>Link to repo:<br><a href=3D"https://github.com/shamazmazum/s=
bcl-dragonfly">https://github.com/shamazmazum/sbcl-dragonfly</a><br></div><=
div><br></div><div>There is a problem nevertheless: use of symbol-value-in-=
thread in sb-concurrency tests causes sbcl to crash (not to ldb, but crash =
completely!).<br>
<br></div><div>So I have some questions:<br></div><div>1. src/runtime/Confi=
g.x86-64-freebsd states that we must use 1:1 threading not m:n threading an=
d uses lthr for that purpose. It seems that there isn't lthr in dragonf=
ly, only lpthread is present. Should I use it? Is 1:1 threading supported? =
(It seems to work with lpthread anyway).<br>
</div><div>2. SBCL uses GCC TLS with (and only with) FreeBSD. I heard somet=
hing about lack of "native" TLS in FreeBSD. Is it true? Is TLS pr=
esent on DragonFly?<br></div><div>3. Can I build and install x86 environmen=
t and virtual kernel on x86-64 machine? I prefer not to use VirtualBox if t=
here is possibility to use vkernel. This is needed to port SBCL to x86 too.=
<br>
</div><div><br></div><div>Sorry for possibly stupid questions, I am new bot=
h to DragonFlyBSD and SBCL internals.<br></div><div><br></div><div>Any help=
of SBCL/Common Lisp hackers would be appreciated. I have really no idea ho=
w to fix sb-concurrency right now.<br>
</div><div></div></div>
--20cf3071c9bc5e889004d91d7c6e--
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]