enable/disable state. Note that it's on-going, and so far I've seen
commits from at least {benno, dfr, imp, jhb}. If you did some of this
e-mail me and I'll add you. Someone let me know when it's done.
Jason Evan's public_html directory.
- Link to archived email messages from docs.freebsd.org, rather than
non existant text files in the local directory.
- Correct link to Chuck Patterson's slides, which reside in ~jasone,
not the local directory.
- Break out lockmgr exclusive and sx/mutex tasks from one another, and
leave the original (completed) movement of mutex pool initialization
task as it's own thing.
- Create the task for moving to purely exclusive locks in VM rather than
lockmgr shared locks. This task will involve implementation, then testing
to see if it actually hurts. If this is possible, it will greatly
simplify the transition to new locking primitives. Assign this to
green since he's expressed willingness to work on it.
- Create the task for moving from lockmgr to either mutexes or exclusive
sxlocks for VM. At that point, it should be possible to start pushing
Giant down into VM somewhere, subject to lack of locking for a few
primitives that will still require it, and for VFS/pmap interactions.
system with a simple exclusive locking scheme, avoiding livelock and
deadlock scenarios using the new locking primitives, per Matt Dillon's
description on freebsd-current.
Obtained from: 200203180048.g2I0mOc40231@apollo.backplane.com
Previously, this stylesheet was incorrectly referenced so user agents
would ignore it, but Apache logs would be spammed with freebsd.css not
found errors.
This is deliberately not connected to the build, as Robert still may
have some updates to add before we make this public.
Notes prepared by: gnn and rwatson
- Alfred has pushed down Giant for a number of fd-related operations,
including read/write/pread/pwrite, +other consumers into the per-subsystem
fileop code. Record this as done.
- Add a task to push down Giant for the remaining such calls, including
readv/writev which currently still require Giant for memory management
in handling struct iovec arrays. Record this as un-owned.
structures behind a 'sellock' to prevent lock order reversals relating
the processes in the select() code. Update the task entry to move it
to the Done section as of today.
