2010-04-27 16:34:05 +04:00
|
|
|
/*
|
|
|
|
* Helpers for getting linearized buffers from iov / filling buffers into iovs
|
|
|
|
*
|
|
|
|
* Copyright IBM, Corp. 2007, 2008
|
|
|
|
* Copyright (C) 2010 Red Hat, Inc.
|
|
|
|
*
|
|
|
|
* Author(s):
|
|
|
|
* Anthony Liguori <aliguori@us.ibm.com>
|
|
|
|
* Amit Shah <amit.shah@redhat.com>
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
* Michael Tokarev <mjt@tls.msk.ru>
|
2010-04-27 16:34:05 +04:00
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2. See
|
|
|
|
* the COPYING file in the top-level directory.
|
2012-01-13 20:44:23 +04:00
|
|
|
*
|
|
|
|
* Contributions after 2012-01-13 are licensed under the terms of the
|
|
|
|
* GNU GPL, version 2 or (at your option) any later version.
|
2010-04-27 16:34:05 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include "iov.h"
|
|
|
|
|
2012-03-14 11:18:54 +04:00
|
|
|
#ifdef _WIN32
|
|
|
|
# include <windows.h>
|
|
|
|
# include <winsock2.h>
|
|
|
|
#else
|
|
|
|
# include <sys/types.h>
|
|
|
|
# include <sys/socket.h>
|
|
|
|
#endif
|
|
|
|
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t iov_from_buf(struct iovec *iov, unsigned int iov_cnt,
|
|
|
|
size_t offset, const void *buf, size_t bytes)
|
2010-04-27 16:34:05 +04:00
|
|
|
{
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t done;
|
2010-04-27 16:34:05 +04:00
|
|
|
unsigned int i;
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
for (i = 0, done = 0; (offset || done < bytes) && i < iov_cnt; i++) {
|
|
|
|
if (offset < iov[i].iov_len) {
|
|
|
|
size_t len = MIN(iov[i].iov_len - offset, bytes - done);
|
|
|
|
memcpy(iov[i].iov_base + offset, buf + done, len);
|
|
|
|
done += len;
|
|
|
|
offset = 0;
|
|
|
|
} else {
|
|
|
|
offset -= iov[i].iov_len;
|
2011-07-11 17:02:23 +04:00
|
|
|
}
|
2010-04-27 16:34:05 +04:00
|
|
|
}
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
assert(offset == 0);
|
|
|
|
return done;
|
2010-04-27 16:34:05 +04:00
|
|
|
}
|
2010-04-27 16:34:06 +04:00
|
|
|
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t iov_to_buf(const struct iovec *iov, const unsigned int iov_cnt,
|
|
|
|
size_t offset, void *buf, size_t bytes)
|
2010-04-27 16:34:06 +04:00
|
|
|
{
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t done;
|
2010-04-27 16:34:06 +04:00
|
|
|
unsigned int i;
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
for (i = 0, done = 0; (offset || done < bytes) && i < iov_cnt; i++) {
|
|
|
|
if (offset < iov[i].iov_len) {
|
|
|
|
size_t len = MIN(iov[i].iov_len - offset, bytes - done);
|
|
|
|
memcpy(buf + done, iov[i].iov_base + offset, len);
|
|
|
|
done += len;
|
|
|
|
offset = 0;
|
|
|
|
} else {
|
|
|
|
offset -= iov[i].iov_len;
|
2010-04-27 16:34:06 +04:00
|
|
|
}
|
2011-07-13 17:16:08 +04:00
|
|
|
}
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
assert(offset == 0);
|
|
|
|
return done;
|
2011-07-13 17:16:08 +04:00
|
|
|
}
|
|
|
|
|
change iov_* function prototypes to be more appropriate
Reorder arguments to be more natural, readable and
consistent with other iov_* functions, and change
argument names, from:
iov_from_buf(iov, iov_cnt, buf, iov_off, size)
to
iov_from_buf(iov, iov_cnt, offset, buf, bytes)
The result becomes natural English:
copy data to this `iov' vector with `iov_cnt'
elements starting at byte offset `offset'
from memory buffer `buf', processing `bytes'
bytes max.
(Try to read the original prototype this way).
Also change iov_clear() to more general iov_memset()
(it uses memset() internally anyway).
While at it, add comments to the header file
describing what the routines actually does.
The patch only renames argumens in the header, but
keeps old names in the implementation. The next
patch will touch actual code to match.
Now, it might look wrong to pay so much attention
to so small things. But we've so many badly designed
interfaces already so the whole thing becomes rather
confusing or error prone. One example of this is
previous commit and small discussion which emerged
from it, with an outcome that the utility functions
like these aren't well-understdandable, leading to
strange usage cases. That's why I paid quite some
attention to this set of functions and a few
others in subsequent patches.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-03-11 18:05:12 +04:00
|
|
|
size_t iov_memset(const struct iovec *iov, const unsigned int iov_cnt,
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t offset, int fillc, size_t bytes)
|
2011-07-13 17:16:08 +04:00
|
|
|
{
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
size_t done;
|
2011-07-13 17:16:08 +04:00
|
|
|
unsigned int i;
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
for (i = 0, done = 0; (offset || done < bytes) && i < iov_cnt; i++) {
|
|
|
|
if (offset < iov[i].iov_len) {
|
|
|
|
size_t len = MIN(iov[i].iov_len - offset, bytes - done);
|
|
|
|
memset(iov[i].iov_base + offset, fillc, len);
|
|
|
|
done += len;
|
|
|
|
offset = 0;
|
|
|
|
} else {
|
|
|
|
offset -= iov[i].iov_len;
|
2011-07-13 17:16:08 +04:00
|
|
|
}
|
2010-04-27 16:34:06 +04:00
|
|
|
}
|
rewrite iov_* functions
This changes implementations of all iov_*
functions, completing the previous step.
All iov_* functions now ensure that this offset
argument is within the iovec (using assertion),
but lets to specify `bytes' value larger than
actual length of the iovec - in this case they
stops at the actual end of iovec. It is also
suggested to use convinient `-1' value as `bytes'
to mean just this -- "up to the end".
There's one very minor semantic change here: new
requiriment is that `offset' points to inside of
iovec. This is checked just at the end of functions
(assert()), it does not actually need to be enforced,
but using any of these functions with offset pointing
past the end of iovec is wrong anyway.
Note: the new code in iov.c uses arithmetic with
void pointers. I thought this is not supported
everywhere and is a GCC extension (indeed, the C
standard does not define void arithmetic). However,
the original code already use void arith in
iov_from_buf() function:
(memcpy(..., buf + buf_off,...)
which apparently works well so far (it is this
way in qemu 1.0). So I left it this way and used
it in other places.
While at it, add a unit-test file test-iov.c,
to check various corner cases with iov_from_buf(),
iov_to_buf() and iov_memset().
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2012-06-07 20:08:19 +04:00
|
|
|
assert(offset == 0);
|
|
|
|
return done;
|
2010-04-27 16:34:06 +04:00
|
|
|
}
|
|
|
|
|
2011-07-11 17:02:23 +04:00
|
|
|
size_t iov_size(const struct iovec *iov, const unsigned int iov_cnt)
|
2010-04-27 16:34:06 +04:00
|
|
|
{
|
|
|
|
size_t len;
|
|
|
|
unsigned int i;
|
|
|
|
|
|
|
|
len = 0;
|
2011-07-11 17:02:23 +04:00
|
|
|
for (i = 0; i < iov_cnt; i++) {
|
2010-04-27 16:34:06 +04:00
|
|
|
len += iov[i].iov_len;
|
|
|
|
}
|
|
|
|
return len;
|
|
|
|
}
|
2011-07-12 15:35:10 +04:00
|
|
|
|
2012-03-14 11:18:54 +04:00
|
|
|
/* helper function for iov_send_recv() */
|
|
|
|
static ssize_t
|
|
|
|
do_send_recv(int sockfd, struct iovec *iov, unsigned iov_cnt, bool do_send)
|
|
|
|
{
|
|
|
|
#if defined CONFIG_IOVEC && defined CONFIG_POSIX
|
|
|
|
ssize_t ret;
|
|
|
|
struct msghdr msg;
|
|
|
|
memset(&msg, 0, sizeof(msg));
|
|
|
|
msg.msg_iov = iov;
|
|
|
|
msg.msg_iovlen = iov_cnt;
|
|
|
|
do {
|
|
|
|
ret = do_send
|
|
|
|
? sendmsg(sockfd, &msg, 0)
|
|
|
|
: recvmsg(sockfd, &msg, 0);
|
|
|
|
} while (ret < 0 && errno == EINTR);
|
|
|
|
return ret;
|
|
|
|
#else
|
|
|
|
/* else send piece-by-piece */
|
|
|
|
/*XXX Note: windows has WSASend() and WSARecv() */
|
2012-07-11 09:09:05 +04:00
|
|
|
unsigned i = 0;
|
|
|
|
ssize_t ret = 0;
|
|
|
|
while (i < iov_cnt) {
|
2012-03-14 11:18:54 +04:00
|
|
|
ssize_t r = do_send
|
|
|
|
? send(sockfd, iov[i].iov_base, iov[i].iov_len, 0)
|
|
|
|
: recv(sockfd, iov[i].iov_base, iov[i].iov_len, 0);
|
|
|
|
if (r > 0) {
|
|
|
|
ret += r;
|
|
|
|
} else if (!r) {
|
|
|
|
break;
|
|
|
|
} else if (errno == EINTR) {
|
|
|
|
continue;
|
|
|
|
} else {
|
|
|
|
/* else it is some "other" error,
|
|
|
|
* only return if there was no data processed. */
|
|
|
|
if (ret == 0) {
|
2012-07-11 09:09:05 +04:00
|
|
|
ret = -1;
|
2012-03-14 11:18:54 +04:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
2012-07-11 09:09:05 +04:00
|
|
|
i++;
|
2012-03-14 11:18:54 +04:00
|
|
|
}
|
2012-07-11 09:09:05 +04:00
|
|
|
return ret;
|
2012-03-14 11:18:54 +04:00
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
|
|
|
ssize_t iov_send_recv(int sockfd, struct iovec *iov, unsigned iov_cnt,
|
|
|
|
size_t offset, size_t bytes,
|
|
|
|
bool do_send)
|
|
|
|
{
|
|
|
|
ssize_t ret;
|
|
|
|
unsigned si, ei; /* start and end indexes */
|
|
|
|
|
|
|
|
/* Find the start position, skipping `offset' bytes:
|
|
|
|
* first, skip all full-sized vector elements, */
|
|
|
|
for (si = 0; si < iov_cnt && offset >= iov[si].iov_len; ++si) {
|
|
|
|
offset -= iov[si].iov_len;
|
|
|
|
}
|
|
|
|
if (offset) {
|
|
|
|
assert(si < iov_cnt);
|
|
|
|
/* second, skip `offset' bytes from the (now) first element,
|
|
|
|
* undo it on exit */
|
|
|
|
iov[si].iov_base += offset;
|
|
|
|
iov[si].iov_len -= offset;
|
|
|
|
}
|
|
|
|
/* Find the end position skipping `bytes' bytes: */
|
|
|
|
/* first, skip all full-sized elements */
|
|
|
|
for (ei = si; ei < iov_cnt && iov[ei].iov_len <= bytes; ++ei) {
|
|
|
|
bytes -= iov[ei].iov_len;
|
|
|
|
}
|
|
|
|
if (bytes) {
|
|
|
|
/* second, fixup the last element, and remember
|
|
|
|
* the length we've cut from the end of it in `bytes' */
|
|
|
|
size_t tail;
|
|
|
|
assert(ei < iov_cnt);
|
|
|
|
assert(iov[ei].iov_len > bytes);
|
|
|
|
tail = iov[ei].iov_len - bytes;
|
|
|
|
iov[ei].iov_len = bytes;
|
|
|
|
bytes = tail; /* bytes is now equal to the tail size */
|
|
|
|
++ei;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = do_send_recv(sockfd, iov + si, ei - si, do_send);
|
|
|
|
|
|
|
|
/* Undo the changes above */
|
|
|
|
if (offset) {
|
|
|
|
iov[si].iov_base -= offset;
|
|
|
|
iov[si].iov_len += offset;
|
|
|
|
}
|
|
|
|
if (bytes) {
|
|
|
|
iov[ei-1].iov_len += bytes;
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2011-07-12 15:35:10 +04:00
|
|
|
void iov_hexdump(const struct iovec *iov, const unsigned int iov_cnt,
|
|
|
|
FILE *fp, const char *prefix, size_t limit)
|
|
|
|
{
|
|
|
|
unsigned int i, v, b;
|
|
|
|
uint8_t *c;
|
|
|
|
|
|
|
|
c = iov[0].iov_base;
|
|
|
|
for (i = 0, v = 0, b = 0; b < limit; i++, b++) {
|
|
|
|
if (i == iov[v].iov_len) {
|
|
|
|
i = 0; v++;
|
|
|
|
if (v == iov_cnt) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
c = iov[v].iov_base;
|
|
|
|
}
|
|
|
|
if ((b % 16) == 0) {
|
|
|
|
fprintf(fp, "%s: %04x:", prefix, b);
|
|
|
|
}
|
|
|
|
if ((b % 4) == 0) {
|
|
|
|
fprintf(fp, " ");
|
|
|
|
}
|
|
|
|
fprintf(fp, " %02x", c[i]);
|
|
|
|
if ((b % 16) == 15) {
|
|
|
|
fprintf(fp, "\n");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if ((b % 16) != 0) {
|
|
|
|
fprintf(fp, "\n");
|
|
|
|
}
|
|
|
|
}
|