From: Jeff Garzik <jeff@garzik.org>
To: hail-devel@vger.kernel.org
Subject: chunkd's get-partial API
Date: Fri, 27 Aug 2010 16:55:15 -0400 [thread overview]
Message-ID: <20100827205515.GA11531@havoc.gtf.org> (raw)
Just as an FYI... these are the chunkd client API changes for GET_PART,
the new chunkd command that retrieves a partial subset of an object.
It's pretty straightforward, adding an (offset, max-length) pair to the
existing GET-related APIs.
diff --git a/include/chunkc.h b/include/chunkc.h
index 1fd7066..d35f1c2 100644
--- a/include/chunkc.h
+++ b/include/chunkc.h
@@ -74,6 +74,19 @@ extern bool stc_get_start(struct st_client *stc, const void *key,
size_t key_len,int *pfd, uint64_t *len);
extern size_t stc_get_recv(struct st_client *stc, void *data, size_t len);
+extern bool stc_get_part(struct st_client *stc, const void *key, size_t key_len,
+ uint64_t offset, uint64_t max_len,
+ size_t (*write_cb)(void *, size_t, size_t, void *),
+ void *user_data);
+extern void *stc_get_part_inline(struct st_client *stc,
+ const void *key, size_t key_len,
+ uint64_t offset, uint64_t max_len,
+ size_t *len);
+extern bool stc_get_part_start(struct st_client *stc, const void *key,
+ size_t key_len,
+ uint64_t offset, uint64_t max_len,
+ int *pfd, uint64_t *len);
+
extern bool stc_put(struct st_client *stc, const void *key, size_t key_len,
size_t (*read_cb)(void *, size_t, size_t, void *),
uint64_t len, void *user_data, uint32_t flags);
@@ -113,6 +126,23 @@ static inline bool stc_get_startz(struct st_client *stc, const char *key,
return stc_get_start(stc, key, strlen(key) + 1, pfd, len);
}
+static inline void *stc_get_part_inlinez(struct st_client *stc,
+ const char *key,
+ uint64_t offset, uint64_t max_len,
+ size_t *len)
+{
+ return stc_get_part_inline(stc, key, strlen(key) + 1, offset, max_len,
+ len);
+}
+
+static inline bool stc_get_part_startz(struct st_client *stc, const char *key,
+ uint64_t offset, uint64_t max_len,
+ int *pfd, uint64_t *len)
+{
+ return stc_get_part_start(stc, key, strlen(key) + 1,
+ offset, max_len, pfd, len);
+}
+
static inline bool stc_put_inlinez(struct st_client *stc, const char *key,
void *data, uint64_t len, uint32_t flags)
{
next reply other threads:[~2010-08-27 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 20:55 Jeff Garzik [this message]
2010-08-27 22:59 ` chunkd's get-partial API Pete Zaitcev
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=20100827205515.GA11531@havoc.gtf.org \
--to=jeff@garzik.org \
--cc=hail-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).