CEPH filesystem development
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/6] ceph: a few more messenger cleanups
Date: Mon, 18 Jun 2012 10:29:12 -0500	[thread overview]
Message-ID: <4FDF4948.10306@inktank.com> (raw)

Here are a few more messenger cleanup patches.

[PATCH 1/6] libceph: encapsulate out message data setup
[PATCH 2/6] libceph: encapsulate advancing msg page
    These two encapsulate some code involved in sending message data
    into separate functions.
[PATCH 3/6] libceph: don't mark footer complete before it is
    This moves the setting of the "FOOTER_COMPLETE" flag so that it
    doesn't get done until the footer really is complete.
[PATCH 4/6] libceph: move init_bio_*() functions up
    This simply moves two functions, preparing for the next patch.
[PATCH 5/6] libceph: move init of bio_iter
    This makes a message's bio_iter field get initialized when
    the rest of the message is initialized, rather than conditionally
    every time any attempt is made to send message data.
[PATCH 6/6] libceph: don't use bio_iter as a flag
    Because bio_iter is now initialized in the "right" place we no
    longer need to use its value as a flag to determine whether it
    needs initialization.

					-Alex

             reply	other threads:[~2012-06-18 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 15:29 Alex Elder [this message]
2012-06-18 15:33 ` [PATCH 1/6] libceph: encapsulate out message data setup Alex Elder
2012-06-18 15:33 ` [PATCH 2/6] libceph: encapsulate advancing msg page Alex Elder
2012-06-18 15:33 ` [PATCH 3/6] libceph: don't mark footer complete before it is Alex Elder
2012-06-18 15:33 ` [PATCH 4/6] libceph: move init_bio_*() functions up Alex Elder
2012-06-18 15:33 ` [PATCH 5/6] libceph: move init of bio_iter Alex Elder
2012-06-18 15:33 ` [PATCH 6/6] libceph: don't use bio_iter as a flag 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=4FDF4948.10306@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox