From: Ming Zhang <mingz@ele.uri.edu>
To: LKML <linux-kernel@vger.kernel.org>
Subject: very weired random io behavior
Date: Fri, 26 Aug 2005 16:08:47 -0400 [thread overview]
Message-ID: <1125086927.5549.121.camel@localhost.localdomain> (raw)
I ran a small test program on a 400GB SATA disk connected to Marvel
chip. Using 2.6.11.12 kernel and get this strange behavior.
# iostat -k -p /dev/sdj
Linux 2.6.11.12 (bakstor2u.localdomain) 08/26/2005
avg-cpu: %user %nice %sys %iowait %idle
0.11 0.00 6.63 54.75 38.51
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
sdj 0.00 0.01 0.00 36 0
start with no io. run program with /dev/sdj and count 10240. i supposed
it should only write 40MB data and no read should be generated. but
result is quite weired. there are almost same amount of read and total
size is around 80MB.
# iostat -k -p /dev/sdj
Linux 2.6.11.12 (bakstor2u.localdomain) 08/26/2005
avg-cpu: %user %nice %sys %iowait %idle
0.11 0.00 6.48 55.65 37.77
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
sdj 4.26 11.31 11.47 80476 81640
pls cc to me.
Thanks!
Ming
---------------------------------------------------
#define _LARGEFILE64_SOURCE
#include <stdlib.h>
#include <sys/types.h>
#include <unistd.h>
#include <fcntl.h>
#include <sys/types.h>
#include <sys/stat.h>
int main(int argc, char *argv[])
{
int n;
int i, count;
char *name;
char buf[4096];
int fd;
if (argc != 3) {
printf("%s name count\n", argv[0]);
exit(1);
}
name = argv[1];
count = atoi(argv[2]);
fd = open(name, O_CREAT|O_WRONLY, S_IRWXU);
for (i = 0; i < count; i++) {
unsigned long x;
x = (rand() >> 1) << 1;
lseek64(fd, x, SEEK_SET);
write(fd, buf, 4096);
}
printf("done\n");
close(fd);
return 0;
}
next reply other threads:[~2005-08-26 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 20:08 Ming Zhang [this message]
2005-08-26 20:18 ` Ming Zhang
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=1125086927.5549.121.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®