CEPH filesystem development
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: ceph-devel@vger.kernel.org
Cc: Sage Weil <sweil@redhat.com>, Zheng Yan <zyan@redhat.com>
Subject: [PATCH 0/3] libceph, ceph: get rid of ack vs commit
Date: Thu, 23 Feb 2017 21:59:18 +0100	[thread overview]
Message-ID: <1487883561-32001-1-git-send-email-idryomov@gmail.com> (raw)

Hello,

This is all straightforward and passes tests, but I'd greatly
appreciate an extra set of eyes on the fs/ceph bits.

Thanks,

                Ilya


Ilya Dryomov (3):
  ceph: remove special ack vs commit behavior
  libceph: get rid of ack vs commit
  libceph, rbd, ceph: WRITE | ONDISK -> WRITE

 drivers/block/rbd.c             |   6 +-
 fs/ceph/addr.c                  |  14 ++---
 fs/ceph/caps.c                  |   2 -
 fs/ceph/file.c                  | 101 ++-------------------------------
 fs/ceph/inode.c                 |   9 ---
 fs/ceph/super.c                 |   1 -
 fs/ceph/super.h                 |   4 +-
 include/linux/ceph/osd_client.h |   6 +-
 net/ceph/cls_lock_client.c      |  12 ++--
 net/ceph/osd_client.c           | 120 ++++++++++------------------------------
 10 files changed, 48 insertions(+), 227 deletions(-)

-- 
2.4.3


             reply	other threads:[~2017-02-23 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 20:59 Ilya Dryomov [this message]
2017-02-23 20:59 ` [PATCH 1/3] ceph: remove special ack vs commit behavior Ilya Dryomov
2017-02-23 23:00   ` Jeff Layton
2017-02-23 20:59 ` [PATCH 2/3] libceph: get rid of ack vs commit Ilya Dryomov
2017-02-23 21:43   ` Sage Weil
2017-02-23 22:18     ` Ilya Dryomov
2017-02-23 23:14   ` Jeff Layton
2017-02-24 11:19     ` Ilya Dryomov
2017-02-23 20:59 ` [PATCH 3/3] libceph, rbd, ceph: WRITE | ONDISK -> WRITE Ilya Dryomov
2017-02-24  1:40   ` Jeff Layton
2017-02-24 14:52 ` [PATCH 0/3] libceph, ceph: get rid of ack vs commit Sage Weil

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=1487883561-32001-1-git-send-email-idryomov@gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.com \
    --cc=zyan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox