From: "William K. Josephson" <wkj@eecs.harvard.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] drawterm and linux 2.4.4 SMP
Date: Sat, 21 Jul 2001 00:59:32 -0400 [thread overview]
Message-ID: <20010721005932.A42689@honk.eecs.harvard.edu> (raw)
In-Reply-To: <20010721023834.60B961998A@mail.cse.psu.edu>; from jmk@plan9.bell-labs.com on Fri, Jul 20, 2001 at 10:38:30PM -0400
On Fri, Jul 20, 2001 at 10:38:30PM -0400, jmk@plan9.bell-labs.com wrote:
> On Fri Jul 20 21:16:24 EDT 2001, crdevilb@mtu.edu wrote:
> > Was there some suggestion or patch anybody had to fix this, or am I
> > going to be digging into the linux kernel to find yet another hack to
> > solve this?
> I haven't looked at that code but from the description it looks like
> the thread switch hack Phil Winterbottom and I did when we ported Inferno
> to Linux a very long time ago. At that time Linux used the task
I haven't looked at the drawterm code in quite a while, but I'd
suggest using the pthreads version. I'm fairly sure that that is what
is done under FreeBSD instead of using their rfork(2) (or the new libc
wrapper in 4.3-stable). The pthreads implementation for Linux is a
good example of how not to use #ifdef (or it was last I looked), but
in general the implementations I've seen appear to be compatible and
stable enough to use on almost all the major Unix derivatives that
mucking around with the tss stuff probably isn't worth it for
something like drawterm. Especially when the kernel changes as often
as it does under Linux.
-WJ
next prev parent reply other threads:[~2001-07-21 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 2:38 jmk
2001-07-21 4:59 ` William K. Josephson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 2:01 David Gordon Hogan
2001-07-22 1:03 Colin DeVilbiss
2001-07-21 9:34 forsyth
2001-07-21 8:19 nigel
2001-07-21 7:37 forsyth
2001-07-21 7:34 forsyth
2001-07-21 1:12 crdevilb
2001-07-21 2:43 ` Alexander Viro
2001-07-21 4:24 ` Ish Rattan
2001-07-21 4:28 ` Ish Rattan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010721005932.A42689@honk.eecs.harvard.edu \
--to=wkj@eecs.harvard.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).