10-25-2005
pread & pwrite are for raw I/O to character devices.
lread & lwrit are I/O to the buffer, not disk
logical read/write means that the I/O was done to a buffer, ie., memory.
Physical I/O is to a device - tty, disk, tape.
The more use the system gets from buffers, the more efficient overall I/O throughput becomes.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I executed the following command in the korn shell:
$ variable1="qwerty" ls | sort
and the shell executed the 'ls | sort' command.
I would have expected an error message from the shell, but instead of that the shell ran the 'ls | sort' command and didn't realize the variable assignement. ... (1 Reply)
Discussion started by: PhilippeCrokaer
1 Replies
2. AIX
hello
with a sar i have this result:
System configuration: lcpu=48 ent=4.00
14:06:37 %usr %sys %wio %idle physc %entc
14:06:39 26 9 3 62 1.63 40.7
14:06:41 26 9 3 63 1.58 39.4
14:06:43 ... (0 Replies)
Discussion started by: pascalbout
0 Replies
3. IP Networking
Hi Guys,
This is really really urgent. Am looking out for some quick answers.
I'm developing a DNS Resolver client that interprets DNS Query repsonses & pass on the needful to DNS applications.
When an ENUM query(modified to an nslookup naptr query) is issued & an NAPTR RR(Resource Record)... (1 Reply)
Discussion started by: smanu
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I get the message NOTICE HTFS :No Space on dev hd (1/104), What does (1/104) mean? Is there any link, I can get material on understanding unix message log?
thanks. (4 Replies)
Discussion started by: scomrade
4 Replies
5. Solaris
Hi
What means Solaris 10 5/09 and Solaris 10 10/09, I mean the suffix 5/09 and 10/09 ?
thx for help. (1 Reply)
Discussion started by: presul
1 Replies
6. Shell Programming and Scripting
I'm writing a Korn script but am having trouble because the shell interprets the asterisk in this case. Can anyone tell me if there is a way to fix this so that grep takes in STDIN without the interpretation?
line="30 09 * * 1-4 /home/user01/bin/start"
echo "$line" | grep 'start' (16 Replies)
Discussion started by: sprucio
16 Replies
7. AIX
On my VIo I see the following for my disks:
$ lspath | grep hdisk6
Enabled hdisk6 fscsi0 200600a0b82193f7,4000000000000
Enabled hdisk6 fscsi0 200700a0b82193f7,4000000000000
Enabled hdisk6 fscsi2 200600a0b82193f8,4000000000000
Failed hdisk6 fscsi2 200700a0b82193f8,4000000000000
$ lspath |... (8 Replies)
Discussion started by: petervg
8 Replies
8. UNIX for Advanced & Expert Users
hi, anyone can help on this piece of truss output?
8094: 0.7028 write(4, 0x0043BE90, 236) = 236
8094: T S H \0\0\0EC020101\0\0\0\0\0\0\0\0\0 "02\0\0 303\0\0 I D
8094: \f %\0\0\0\0 2\0F67F\0\0\0\0 @06FFC99A ;
8094: L D6\0 303
8094: ... (6 Replies)
Discussion started by: ghostdog74
6 Replies
9. UNIX for Advanced & Expert Users
hi,
working on Solaris 10. need your help on ping behaviour that I encountered.
I ping from source to destination
-bash-3.2# ping -s -t 128 10.10.10.200
PING 10.10.10.200: 56 data bytes <===== stops here for 2 minutues before getting reply back
64 bytes from 10.10.10.200:... (9 Replies)
Discussion started by: ghostdog74
9 Replies
RK(4) Kernel Interfaces Manual RK(4)
NAME
rk - RK-11/RK03 or RK05 disk
DESCRIPTION
Rk? refers to an entire disk as a single sequentially-addressed file. Its 256-word blocks are numbered 0 to 4871. Minor device numbers
are drive numbers on one controller.
The rk files discussed above access the disk via the system's normal buffering mechanism and may be read and written without regard to
physical disk records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or
write buffer. A single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when
many words are transmitted. The names of the raw RK files begin with rrk and end with a number which selects the same disk as the corre-
sponding rk file.
In raw I/O the buffer must begin on a word boundary, and counts should be a multiple of 512 bytes (a disk block). Likewise seek calls
should specify a multiple of 512 bytes.
FILES
/dev/rk?, /dev/rrk?
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
RK(4)