From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/5] ceph: abstract message data information setting
Date: Tue, 05 Mar 2013 07:51:21 -0600 [thread overview]
Message-ID: <5135F859.1090606@inktank.com> (raw)
The first two of these were posted before, but they ran into
trouble because assertions that data information fields in
ceph messages got set only once were failing. Now those
assertions are commented out--initially.
The third and fourth patches in this series address the
reasons the assertions could fail, by changing the osd
client to only set message data fields once, and by changing
the mds client to only set them if there is data to be sent.
The final patch activates those commented-out assertions.
These are available in the branch "review/wip-abstract_data"
in the ceph-client git repository.
-Alex
[PATCH 1/5] libceph: isolate message page field manipulation
[PATCH 2/5] libceph: isolate other message data fields
[PATCH 3/5] ceph: only set message data pointers if non-empty
[PATCH 4/5] libceph: set response data fields earlier
[PATCH 5/5] libceph: activate message data assignment checks
next reply other threads:[~2013-03-05 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 13:51 Alex Elder [this message]
2013-03-05 13:52 ` [PATCH 1/5] libceph: isolate message page field manipulation Alex Elder
2013-03-05 16:03 ` Alex Elder
2013-03-05 13:52 ` [PATCH 2/5] libceph: isolate other message data fields Alex Elder
2013-03-05 13:53 ` [PATCH 3/5] ceph: only set message data pointers if non-empty Alex Elder
2013-03-05 21:20 ` Greg Farnum
2013-03-05 13:53 ` [PATCH 4/5] libceph: set response data fields earlier Alex Elder
2013-03-05 13:53 ` [PATCH 5/5] libceph: activate message data assignment checks Alex Elder
2013-03-05 21:21 ` Greg Farnum
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=5135F859.1090606@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.