From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/4] libceph: kill the "trail" portion of message data
Date: Sun, 10 Mar 2013 15:35:15 -0500 [thread overview]
Message-ID: <513CEE83.4040900@inktank.com> (raw)
The trail portion of message data was added to support
two distinct sets of data for an osd request--one a
pagelist for providing parameters to object method
calls; and a second a page array for receiving data
back from the result of such a call.
It's always been a bit of a weird thing bolted onto
a message though, and with the rework of the messenger
code it can now be removed.
This series eliminates the trail by allowing the osd
client to record a (non-trail) pagelist for data, and
using the fact that we now distinguish incoming from
outgoing data to allow that to be specified distinct
from the page array used for the incoming response.
Having done this, we can eliminate the trail from the
ceph message structure, and then that allows some
code to be simplified.
These patches are available in the "review/wip-kill-trail"
branch of the ceph-client git repository. That branch
is based on branch "review/wip-cursor".
-Alex
[PATCH 1/4] libceph: have osd requests support pagelist data
[PATCH 2/4] libceph: kill osd request r_trail
[PATCH 3/4] libceph: kill message trail
[PATCH 4/4] libceph: more cleanup of write_partial_msg_pages()
next reply other threads:[~2013-03-10 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 20:35 Alex Elder [this message]
2013-03-10 20:36 ` [PATCH 1/4] libceph: have osd requests support pagelist data Alex Elder
2013-03-10 20:36 ` [PATCH 2/4] libceph: kill osd request r_trail Alex Elder
2013-03-10 20:36 ` [PATCH 3/4] libceph: kill message trail Alex Elder
2013-03-10 20:36 ` [PATCH 4/4] libceph: more cleanup of write_partial_msg_pages() Alex Elder
2013-03-11 5:08 ` [PATCH 4/4, v2] " Alex Elder
2013-03-11 22:44 ` [PATCH 0/4] libceph: kill the "trail" portion of message data Josh Durgin
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=513CEE83.4040900@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.