Home
last modified time | relevance | path

Searched hist:"8320 d61b" (Results 1 – 7 of 7) sorted by relevance

/xv6-public/
H A Dfs.hdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Dlog.cdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Dmkfs.cdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Dfs.cdiff 82638c01 Wed Mar 20 17:28:13 GMT 2019 Dan Cross <cross@gajendra.net> Avoid rereading the superblock in bfree

The superblock is read when the first process returns to
userspace (via the call to `iinit` from the first invocation of
`forkret`, when `first` is still set to 1) and cached in a
global; it is treated as immutable from that point on. There is
no reason to re-read it in bfree.

Removing this call seems to have simply been missed in 8320d61b
when this general area was last touched. Remove it now to avoid
potential confusion.

Signed-off-by: Dan Cross <cross@gajendra.net>
diff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Ddefs.hdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Dproc.cdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.
H A Dmain.cdiff 8320d61b Sat Jun 27 16:39:13 GMT 2015 Frans Kaashoek <kaashoek@mit.edu> Pick up where i left off in april:
- move log into metadata part of disk, so that marking
that the log's blocks are in use falls out for free
- superblock describes the whole disk (sizes and offets)
- sizes and offsets are computed in one place (mkfs) and
the rest of the code refers to the superblock for these values,
instead of recomputing them.