From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Edward Z. Yang <ezyang@mit.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Inotify support for Maildirs. (FIRST DRAFT)
Date: Mon, 03 Sep 2012 13:02:26 -0300 [thread overview]
Message-ID: <1346688000-sup-4643@alvh.no-ip.org> (raw)
In-Reply-To: <1346648395-sup-4546@javelin>
Excerpts from Edward Z. Yang's message of lun sep 03 02:00:59 -0300 2012:
> The locking is a downright crime (where's the STM when you need it),
> and it's still racy, but it should work OK.
Hm. I tried this but ran into trouble: I currently run branch "next",
and your patch doesn't apply there; so I tried your ~ezyang fork and
branch maildir-sync there, but I find that when in that branch (with or
without this patch), Sup seems to eat 100% of a CPU core doing
clock_gettime() and select() continuously. Not sure what's happening.
I assume you don't see that behavior.
--
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2012-09-03 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 15:17 [sup-devel] inotify support for Maildir mailboxes Edward Z. Yang
2012-08-21 16:00 ` Alvaro Herrera
2012-09-03 4:59 ` [sup-devel] [PATCH] Inotify support for Maildirs. (FIRST DRAFT) Edward Z. Yang
2012-09-03 5:00 ` Edward Z. Yang
2012-09-03 16:02 ` Alvaro Herrera [this message]
2012-09-03 16:07 ` Alvaro Herrera
2012-09-03 16:10 ` ezyang
2012-09-03 18:09 ` Edward Z. Yang
2012-09-03 18:29 ` Edward Z. Yang
2012-09-03 18:42 ` Alvaro Herrera
2012-09-03 18:49 ` Edward Z. Yang
2012-09-03 19:27 ` Edward Z. Yang
2012-09-03 23:31 ` Edward Z. Yang
2012-09-04 16:06 ` Edward Z. Yang
2012-09-04 18:09 ` Alvaro Herrera
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=1346688000-sup-4643@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--cc=ezyang@mit.edu \
--cc=sup-devel@rubyforge.org \
/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