From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/3] diotest6: test readv/writev not read/write
Date: Wed, 15 Mar 2017 11:31:12 +0100 [thread overview]
Message-ID: <20170315103112.GB17618@rei.lan> (raw)
In-Reply-To: <20170302133323.5262-2-eguan@redhat.com>
Hi!
> - if (!buf1 || !buf2) {
> - tst_resm(TBROK | TERRNO, "valloc() failed");
> - free(buf1);
> - free(buf2);
> + /* allocate read/write io vectors */
> + iov_r = calloc(nvector, sizeof(*iov_r));
> + if (!iov_r) {
> + tst_resm(TBROK | TERRNO, "calloc failed for iov_r array");
> + return -1;
> + }
> + iov_w = calloc(nvector, sizeof(*iov_w));
> + if (!iov_w) {
> + tst_resm(TBROK | TERRNO, "calloc failed for iov_w array");
> + free(iov_r);
> return -1;
> }
Doing free(NULL) is no-op. So we can simplify this code by allocating
both arrays at once and then checking if !iow_r || !iow_w just like we
did with the normal buffers.
> - /* Allocate for buffers and data pointers */
> - seekoff = offset + bufsize * childnum;
> + /* allocate buffers and setup read/write io vectors */
> + for (i = 0, iovp = iov_r; i < nvector; iovp++, i++) {
> + iovp->iov_base = valloc(bufsize);
> + if (!iovp->iov_base) {
> + tst_resm(TBROK | TERRNO, "valloc error iov_r[%d]", i);
> + goto free_out;
> + }
> + iovp->iov_len = bufsize;
> + }
Uh, why do we increment both iovp and i here?
When we can simply do:
for (i = 0; i < nvector; i++) {
iovp[i].iov_base = valloc(bufsize);
...
}
> + for (i = 0, iovp = iov_w; i < nvector; iovp++, i++) {
> + iovp->iov_base = valloc(bufsize);
> + if (!iovp->iov_base) {
> + tst_resm(TBROK | TERRNO, "valloc error iov_w[%d]", i);
> + goto free_out;
> + }
> + iovp->iov_len = bufsize;
> + }
Here as well.
> /* seek, write, read and verify */
> + seekoff = offset + bufsize * childnum * nvector;
> for (i = 0; i < iter; i++) {
> - fillbuf(buf1, bufsize, childnum+i);
> + vfillbuf(iov_w, nvector, childnum+i);
>
> if (lseek(fd_w, seekoff, SEEK_SET) < 0) {
> tst_resm(TFAIL, "lseek before write failed: %s",
> strerror(errno));
> - return (-1);
> + goto free_out;
> }
> - if (write(fd_w, buf1, bufsize) < bufsize) {
> - tst_resm(TFAIL, "write failed: %s", strerror(errno));
> - return (-1);
> + if (writev(fd_w, iov_w, nvector) < 0) {
> + tst_resm(TFAIL, "writev failed: %s", strerror(errno));
> + goto free_out;
> }
We have to check here that the whole vector was written as well.
> if (action == READ_DIRECT) {
> /* Make sure data is on to disk before read */
> if (fsync(fd_w) < 0) {
> tst_resm(TFAIL, "fsync failed: %s",
> strerror(errno));
> - return (-1);
> + goto free_out;
> }
> }
> if (lseek(fd_r, seekoff, SEEK_SET) < 0) {
> tst_resm(TFAIL, "lseek before read failed: %s",
> strerror(errno));
> - return (-1);
> + goto free_out;
> }
> - int ret;
> - if ((ret = read(fd_r, buf2, bufsize)) < bufsize) {
> - tst_resm(TFAIL, "read failed: %s", strerror(errno));
> - return (-1);
> + if (readv(fd_r, iov_r, nvector) < 0) {
> + tst_resm(TFAIL, "readv failed: %s", strerror(errno));
> + goto free_out;
> }
Here as well.
> - if (bufcmp(buf1, buf2, bufsize) != 0) {
> + if (vbufcmp(iov_w, iov_r, nvector) != 0) {
> tst_resm(TFAIL, "comparsion failed. Child=%d offset=%d",
> childnum, (int)seekoff);
> - return (-1);
> + goto free_out;
> }
> }
> - return 0;
> + ret = 0;
> +
> +free_out:
I would call this label err: or just out: but that is minor.
> + for (i = 0, iovp = iov_r; i < nvector; iovp++, i++)
> + free(iovp->iov_base);
> + for (i = 0, iovp = iov_w; i < nvector; iovp++, i++)
> + free(iovp->iov_base);
> + free(iov_r);
> + free(iov_w);
> + return ret;
> }
>
> /*
> --
> 2.9.3
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-03-15 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 13:33 [LTP] [PATCH 1/3] diotest: use user specified bufsize correctly Eryu Guan
2017-03-02 13:33 ` [LTP] [PATCH 2/3] diotest6: test readv/writev not read/write Eryu Guan
2017-03-15 10:31 ` Cyril Hrubis [this message]
2017-03-15 10:48 ` Eryu Guan
2017-03-02 13:33 ` [LTP] [PATCH 3/3] runtest/dio: enable dio29/30 Eryu Guan
2017-03-15 10:34 ` Cyril Hrubis
2017-03-15 10:13 ` [LTP] [PATCH 1/3] diotest: use user specified bufsize correctly Cyril Hrubis
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=20170315103112.GB17618@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.