From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Sup annoyances
Date: Mon, 08 Jun 2009 22:38:08 -0400 [thread overview]
Message-ID: <1244515056-sup-4758@javelin> (raw)
In-Reply-To: <1244481844-sup-9094@entry>
Excerpts from William Morgan's message of Mon Jun 08 14:00:23 -0400 2009:
> > 3. Polling and loading of threads should started, asynchronously, at
> > the same time.
>
> > Loading of threads should not hose my CPU.
>
> Agreed. Please fix.
It appears that polling blocks on loading threads, so it doesn't help
to fix that until we fix the thread loading code.
Cheers,
Edward
next prev parent reply other threads:[~2009-06-09 2:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 6:54 Edward Z. Yang
2009-06-06 6:56 ` Edward Z. Yang
[not found] ` <1244308338-sup-4735@cabinet>
2009-06-06 18:17 ` Edward Z. Yang
2009-06-08 18:00 ` William Morgan
2009-06-08 23:14 ` Edward Z. Yang
2009-06-08 23:46 ` William Morgan
2009-06-09 2:13 ` Edward Z. Yang
2009-06-09 2:23 ` Edward Z. Yang
2009-06-09 2:35 ` Edward Z. Yang
2009-06-09 17:40 ` William Morgan
2009-06-11 3:18 ` Edward Z. Yang
2009-06-09 17:48 ` William Morgan
2009-06-11 3:19 ` Edward Z. Yang
2009-06-09 17:32 ` William Morgan
2009-06-09 2:38 ` Edward Z. Yang [this message]
2009-06-09 17:45 ` William Morgan
2009-06-09 3:00 ` Edward Z. Yang
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=1244515056-sup-4758@javelin \
--to=ezyang@mit.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