From: Alex Elder <elder@inktank.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/5] libceph clean up con_work()
Date: Tue, 19 Feb 2013 18:51:33 -0600 [thread overview]
Message-ID: <51241E15.80903@inktank.com> (raw)
This series cleans up con_work() a bit. The original motivation
was to get rid of a warning issued by the sparse utility, but
addressing that required a little rework and it was fairly
straightforward once that was done to make that function
fairly simple.
The problem sparse reported was really due to sparse not
being able to follow the logic between multiple functions
that together implement locking. The result of these
changes makes both acquiring and releasing the connection
mutex occur in con_work().
-Alex
[PATCH 1/5] libceph: encapsulate connection backoff
[PATCH 2/5] libceph: separate non-locked fault handling
[PATCH 3/5] libceph: use a flag to indicate a fault has occurred
[PATCH 4/5] libceph: use a do..while loop in con_work()
[PATCH 5/5] libceph: indent properly
next reply other threads:[~2013-02-20 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 0:51 Alex Elder [this message]
2013-02-20 0:55 ` [PATCH 1/5] libceph: encapsulate connection backoff Alex Elder
2013-02-20 0:55 ` [PATCH 2/5] libceph: separate non-locked fault handling Alex Elder
2013-02-20 0:56 ` [PATCH 3/5] libceph: use a flag to indicate a fault has occurred Alex Elder
2013-02-20 0:56 ` [PATCH 4/5] libceph: use a do..while loop in con_work() Alex Elder
2013-02-20 0:57 ` [PATCH 5/5] libceph: indent properly Alex Elder
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=51241E15.80903@inktank.com \
--to=elder@inktank.com \
--cc=ceph-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.