From: Jeff Layton <jlayton@kernel.org>
To: ceph-devel@vger.kernel.org
Cc: idryomov@gmail.com
Subject: [PATCH 0/4] libceph/ceph: cleanups and move more into ceph.ko
Date: Wed, 1 Jul 2020 11:54:42 -0400 [thread overview]
Message-ID: <20200701155446.41141-1-jlayton@kernel.org> (raw)
This is just a small set of cleanups, with a final patch that moves a
chunk of cephfs-specific code out of libceph.ko and into ceph.ko. There
should be no functional changes here.
Jeff Layton (4):
libceph: just have osd_req_op_init return a pointer
libceph: refactor osdc request initialization
libceph: rename __ceph_osdc_alloc_messages to ceph_osdc_alloc_num_messages
libceph/ceph: move ceph_osdc_new_request into ceph.ko
fs/ceph/Makefile | 2 +-
fs/ceph/addr.c | 1 +
fs/ceph/file.c | 1 +
fs/ceph/osdc.c | 113 +++++++++++++++++++
fs/ceph/osdc.h | 16 +++
include/linux/ceph/osd_client.h | 19 ++--
net/ceph/osd_client.c | 185 ++++++--------------------------
7 files changed, 173 insertions(+), 164 deletions(-)
create mode 100644 fs/ceph/osdc.c
create mode 100644 fs/ceph/osdc.h
--
2.26.2
next reply other threads:[~2020-07-01 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 15:54 Jeff Layton [this message]
2020-07-01 15:54 ` [PATCH 1/4] libceph: just have osd_req_op_init return a pointer Jeff Layton
2020-07-06 16:41 ` Jeff Layton
2020-07-08 10:18 ` Ilya Dryomov
2020-07-01 15:54 ` [PATCH 2/4] libceph: refactor osdc request initialization Jeff Layton
2020-07-01 18:08 ` Ilya Dryomov
2020-07-01 18:24 ` Jeff Layton
2020-07-01 19:25 ` Ilya Dryomov
2020-07-01 15:54 ` [PATCH 3/4] libceph: rename __ceph_osdc_alloc_messages to ceph_osdc_alloc_num_messages Jeff Layton
2020-07-01 18:48 ` Ilya Dryomov
2020-07-01 19:17 ` Jeff Layton
2020-07-01 19:40 ` Ilya Dryomov
2020-07-01 19:51 ` Jeff Layton
2020-07-01 15:54 ` [PATCH 4/4] libceph/ceph: move ceph_osdc_new_request into ceph.ko Jeff Layton
2020-07-01 19:15 ` Ilya Dryomov
2020-07-01 19:22 ` Jeff Layton
2020-07-01 20:04 ` Ilya Dryomov
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=20200701155446.41141-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
/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.