diff --git a/en/releases/5.4R/todo.sgml b/en/releases/5.4R/todo.sgml index a178e87fe2..9a75a7eb6c 100644 --- a/en/releases/5.4R/todo.sgml +++ b/en/releases/5.4R/todo.sgml @@ -1,243 +1,242 @@ - + %includes; %developers; N/A"> Done"> In progress"> Needs testing"> Not done"> Unknown"> ]> &header;

Open Issues

This is the beginning of a list of open issues that need to be worked on or resolved for FreeBSD 5.4. If you have any updates for this list, please e-mail re@FreeBSD.org. The feature list for 5.4 is still a work in progress, so items may be added, removed, or modified before we're done.

Show stopper defects for 5.4-RELEASE

- - - - - - -
Issue Status Responsible Description
Deadlock under heavy network load on systems with more than 4 CPUs &status.wip; &a.rwatson; A deadlock of unknown origin has started to appear on systems with 4 or more real CPUs when under heavy TCP load.
IPFilter mpsafe fixes&status.wip;&a.rwatson;IPFilter is currently not mpsafe but doesn't run with Giant.

Required features for 5.4-RELEASE

- - - - - - - - - - - - - - - +
Issue Status Responsible Description
Update sysinstall to handle separate packages CD&status.wip;&a.jhb;Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11
busdma fixes&status.wip;&a.scottl;More work is needed on busdma to fix bounce buffer problems.
ATAPI CDROMs in PIO mode during install &status.wip;&a.jhb;&a.kensmith; People are having difficulties with various ATAPI CDROMs on various architectures. We need to either do all installs in PIO mode or provide a boot menu method of selecting it.

Desired features for 5.4-RELEASE

- - - - - - - - - - - - - -
Issue Status Responsible Description
ACL_MASK override of umask support in UFS &status.new; &a.rwatson; Many systems supporting POSIX.1e ACLs permit a minor violation to that specification, in which the ACL_MASK entry overrides the umask, rather than being intersected with it. The resulting semantics can be useful in group-oriented environments, and as such would be very helpful on FreeBSD.
Entropy harvesting optimizations &status.wip; &a.rwatson;, &a.markm; Entropy harvesting in the interrupt and incoming packet paths currently involves a large number of mutex operations. In order to improve performance, it is desirable to reduce the number of mutex operations substantially. Improvements in the harvesting locking scheme have been merged to 6.x, but are considered too risky at this stage to be merged to 5.x until after 5.3.
KAME IPSEC without the Giant Lock &status.wip; &a.gnn; Currently, the KAME IPSEC implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with the KAME IPSEC implementation (not FAST_IPSEC) to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for KAME IPSEC so that it can run without the Giant lock.
All Network Interface Drivers MPSAFE &status.wip; -- Currently, some network interface drivers are not safe without the Giant lock due to missing synchronization. These drivers are protected by running non-INTR_MPSAFE and with the IFF_NEEDSGIANT flag set, which cause interrupt threads to acquire the Giant lock before executing the driver's interrupt handler, and to perform if_start (interface transmit start) asynchronously once the Giant lock can be acquired. This results in these drivers performing less well due to increased lock contention, decreased ability to preempt, and latency associated with asynchronous launching of latency-critical events. For 5.4, all network drivers should be able to operate without the Giant lock.
NetIPX without the Giant Lock &status.wip; &a.rwatson; Currently, the IPX/SPX (netipx) implementation contains inadequate locking to operate without the Giant lock over the network stack, forcing kernels compiled with IPX support to run the network stack with the Giant lock, reducing parallelism, increasing lock contention, and increasing latency by preventing preemption. For 5.4-RELEASE, it is desirable to complete the locking work for IPX so that it can run without the Giant lock.
Fix regression in file(1) -- -- The new version of file(1) does not cross-build properly. If sparc64 executables are built on i386 the compiled magic numbers file that gets installed is wrong and file(1) doesn't work properly.
AMR driver MPSAFE&status.wip;&a.scottl;Making the AMR driver MPSAFE will greatly increase its performance.
SCHED_ULE update &status.new; -- Many improvements have been made to the ULE scheduler in 6-CURRENT. These should be merged back to 5.4.
CARP support&status.wip;&a.glebius;Common Address Redundancy Protocol allows multiple hosts on the same - local network to share a set of IP addresses.

Documentation items that must be resolved for 5.4

Issue Status Responsible Description

Testing focuses for 5.4-RELEASE

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Issue Status Responsible Description
File descriptor locking &status.done; &a.jeff; File descriptor locking needs to be merged back from HEAD.
IPFilter mpsafe fixes&status.done;&a.rwatson;IPFilter is currently not mpsafe but doesn't run with Giant.
Update sysinstall to handle separate packages CD&status.done;&a.jhb;Avoid the need for a disc1-gnome/disc1-kde as was done for 4.11
busdma fixes&status.done;&a.scottl;More work is needed on busdma to fix bounce buffer problems.
AMR driver MPSAFE&status.done;&a.scottl;Making the AMR driver MPSAFE will greatly increase its performance.
CARP support&status.done;&a.glebius;Common Address Redundancy Protocol allows multiple hosts on the same + local network to share a set of IP addresses.
&footer;