From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH REPOST 0/2] libceph: embed r_trail struct in ceph_osd_request()
Date: Thu, 03 Jan 2013 17:34:33 -0600 [thread overview]
Message-ID: <50E61589.6080900@inktank.com> (raw)
This series simplifies some handling of osd client message
handling by using an initialized ceph_pagelist structure
to refer to the trail portion of a ceph_osd_request rather
than using a null pointer to represent "not there".
-Alex
[PATCH REPOST 1/2] libceph: always allow trail in osd request
[PATCH REPOST 2/2] libceph: kill op_needs_trail()
next reply other threads:[~2013-01-03 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 23:34 Alex Elder [this message]
2013-01-03 23:35 ` [PATCH REPOST 1/2] libceph: always allow trail in osd request Alex Elder
2013-01-03 23:35 ` [PATCH REPOST 2/2] libceph: kill op_needs_trail() Alex Elder
2013-01-16 22:50 ` [PATCH REPOST 0/2] libceph: embed r_trail struct in ceph_osd_request() 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=50E61589.6080900@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.