1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
[[!meta copyright="Copyright © 2008, 2010, 2011 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!meta title="I/O Path"]]
[[!tag open_issue_documentation]] <!-- Someone still needs to make a pass over
this text. -->
[[!toc]]
# `read`, [[libtrivfs]]
[[glibc]]'s `read` is in `glibc/sysdeps/mach/hurd/read.c:__libc_read`.
A buffer (and its size) to store the to-be-read data in is supplied by the
caller of `read`.
> `__libc_read` calls `glibc/hurd/fd-read.c:_hurd_fd_read`.
>> `_hurd_fd_read` calls `__io_read`, which is an [[RPC]]:
>> `hurd/hurd/io.defs:io_read`.
>>> Enter user-side RPC stub `glibc.obj/hurd/RPC_io_read.c:__io_read`. Process
>>> stuff, switch to kernel, etc.
(For example) [[translator/hello]] server, [[libtrivfs]]-based. Enter
server-side RPC stub `hurd.obj/libtrivfs/ioServer.c:_Xio_read`. Process stuff,
call `hurd/trans/hello.c:trivfs_S_io_read`.
A 2048 byte buffer is provided.
> `trivfs_S_io_read`. Depending on the internal state, either a new memory
> region is set-up (and returned as out-of-line data), or the desired amount of
> data is returned in-line.
Back in `_Xio_read`.
If the 2048 byte buffer is not decided to be used (out-of-line case or bigger
than 2048 bytes case; server decides to instead provide a new memory region),
the [[`dealloc`|microkernel/mach/mig/documentation/dealloc]] flag is being set,
which causes Mach to unmap that memory region from the server's address space,
i.e., doing a memory *move* from the server to the client.
Leave server-side RPC stub `_Xio_read`.
>>> Return from kernel, continue client-side RPC stub `io_read`. Have to copy
>>> data. Three cases: out-of-line data (pass pointer to memory area);
>>> returned more data than fits into the originally supplied buffer (allocate
>>> new buffer, copy all data into it, pass pointer of new buffer); otherwise
>>> copy as much data as is available into the originally supplied buffer.
>>> I.e., in all cases *all* data which was provided by the server is made
>>> available to the caller.
>> Back in `_hurd_fd_read`. If a new buffer has been allocated previously, or
>> the out-of-line mechanism has been used, the returned data now has to be
>> copied into the originally supplied buffer. If the server returned more
>> data than requested, this is a [[protocol_violation|EGRATUITOUS]].
> Back in `__libc_read`.
# `read`, [[hurd/translator/ext2fs]]/[[hurd/libdiskfs]]
(For example) [[translator/ext2fs]] server, enter server-side RPC stub
`hurd.obj/libdiskfs/ioServer.c:_Xio_read`. Process stuff, call
`hurd/libdiskfs/io-read.c:diskfs_S_io_read`.
A 2048 byte buffer is provided.
> `diskfs_S_io_read` calls `_diskfs_rdwr_internal`.
>> That calls `hurd/libpager/pager-memcpy.c:pager_memcpy`, which usually
>> basically just tells the kernel to virtually project the memory object
>> corresponding to the file in the caller process's memory. No read is
>> actually done.
* Then, when the process actually reads the data, the kernel gets the user
page fault (`gnumach/i386/i386/trap.c:user_trap`), which calls `vm_fault`,
etc., until actually getting to `gnumach/vm/vm_fault/vm_fault_page` which
eventually calls `memory_object_data_request`, which is an [[RPC]], i.e.,
that actually results into the [[translator/ext2fs]] server calling
`hurd/libpager/data-request.c:_pager_seqnos_memory_object_data_request`.
* That calls `hurd/ext2fs/pager.c:pager_read_page`, which looks for where the
data is on the disk, and eventually calls
`hurd/libstore/rdwr.c:store_read`, which eventually calls `device_read`,
which is an [[RPC]], i.e., that actually gets into the kernel calling
`gnumach/linux/dev/glue/block.c:device_read`.
* ext2fs eventually finishes the data_request() function, the kernel installs
the page into the process that got a fault.
# Documentation
* In [*Linux kernel design patterns - part
3*](http://lwn.net/Articles/336262/) (2009-06-22), Neil Brown gives a
nice overview of the related layering inside the Linux kernel,
including the VFS layer, page cache and directory entry cache
(dcache).
|
