All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Project Hail <hail-devel@vger.kernel.org>
Subject: chunkd thread work
Date: Sun, 01 Nov 2009 23:21:55 -0500	[thread overview]
Message-ID: <4AEE5E63.4030101@garzik.org> (raw)

I removed libevent support from chunkd, because I felt it was blocking 
the multi-threading of chunkd to an unfortunate degree.  libevent does 
not provide any protection for multiple threads adding and removing 
themselves to a single poll-set.

Multi-threading chunkd should enable us to reach our full I/O throughput 
potential through parallelization.  It will also enable useful 
administrative tasks such as background checksum verification.

	Jeff




commit 47a916242eb795b27ca86cb68a25135a14741b5f
Author: Jeff Garzik <jeff@garzik.org>
Date:   Sun Nov 1 23:11:18 2009 -0500

     chunkd: drop libevent support, due to lack of thread-friendliness

     libevent does not support a single poll-set being manipulated
     simultaneously by multiple threads, so it is replaced with a
     poll(2)-based mechanism highly similar to cld's.

     An epoll mechanism would be a logical next-step.

     Signed-off-by: Jeff Garzik <jgarzik@redhat.com>

commit 441eb192ef5d68e6d563f045a3c061d9bc403684
Author: Jeff Garzik <jeff@garzik.org>
Date:   Sun Nov 1 20:39:09 2009 -0500

     chunkd: add cli_wr_set_poll() to isolate libevent usage

     Signed-off-by: Jeff Garzik <jgarzik@redhat.com>

             reply	other threads:[~2009-11-02  4:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  4:21 Jeff Garzik [this message]
2009-11-02  4:26 ` chunkd thread work Pete Zaitcev

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=4AEE5E63.4030101@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.