From: Christoph Hellwig <hch@infradead.org>
To: David Disseldorp <ddiss@suse.de>
Cc: mchristi@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] rbd_tcm cluster COMPARE AND WRITE
Date: Tue, 28 Jul 2015 23:58:56 -0700 [thread overview]
Message-ID: <20150729065856.GC27890@infradead.org> (raw)
In-Reply-To: <1438132552-14673-1-git-send-email-ddiss@suse.de>
Hi David,
please introduce a proper compare and write API at the block layer
instead of bypassing it. Thanks!
next prev parent reply other threads:[~2015-07-29 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 1:15 [RFC PATCH 0/5] rbd_tcm cluster COMPARE AND WRITE David Disseldorp
2015-07-29 1:15 ` [RFC PATCH 1/5] SQUASH rbd/locking: remove rbd_warn() carriage returns David Disseldorp
2015-07-29 1:15 ` [RFC PATCH 2/5] SQUASH rbd: fix recursive BLK_DEV_RBD_TCM dependency David Disseldorp
2015-07-29 1:15 ` [RFC PATCH 3/5] rbd: export rbd_dev_[un]lock() David Disseldorp
2015-07-29 1:15 ` [RFC PATCH 4/5] drivers/rbd_tcm: Add cluster API CAW locking hooks David Disseldorp
2015-07-29 1:15 ` [RFC PATCH 5/5] target/core_sbc: use cluster API hooks for COMPARE AND WRITE David Disseldorp
2015-07-29 6:58 ` Christoph Hellwig [this message]
2015-07-29 9:31 ` [RFC PATCH 0/5] rbd_tcm cluster " Mike Christie
2015-07-29 10:04 ` David Disseldorp
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=20150729065856.GC27890@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ddiss@suse.de \
--cc=mchristi@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 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.