What is claimed is:
1. A system for the evacuation of individuals trapped in multiple story buildings by gliding down a tubular rescue sleeve, stored in a compact package form located at an elevated story of the building, comprising:
a sleeve composed of sections, each section being made of a sheet material strengthened by a circumferential rigid support member;
a first tension cable stretched along the sleeve, following the top generatrix thereof, being freely passed through respective eyelet means mounted to the support members;
means for selectively ejecting and unfolding the sleeve along the first tension cable down to ground level; and
means for tying the first tension cable to a remotely located stationary object.
2. The system as claimed in claim 1 further comprising a second tension cable stretched along the sleeve following the bottom generatrix thereof, being freely passed through respective eyelet means mounted to the support members.
3. The system as claimed in claim 2 wherein the first and the second cables are threaded through every second eyelet, respectively, in a staggered order.
4. The system as claimed in claim 3 further comprising a winch system for winding the first and second cables into a dedicated location at the said elevated building story so that the sleeve becomes folded into the said compact package form.
5. The system as claimed in claim 4 wherein the first and second cables are each wound through a guide tube, the vertical distance between the guide tubes exceeds the distance between the top and the bottom eyelets, so that the sleeve becomes folded in a zig-zag, space-saving order.
6. The system as claimed in claim 5 wherein coil springs are located in each guide tube around their respective cable.
7. The system as claimed in claim 6 wherein a pair of winch systems are provided, each comprising a drum around which the cables are wound.
8. The system as claimed in claim 7 wherein the winch systems comprise means for releasing their drums to enable the said ejecting and unfolding of the sleeve.
9. The system as claimed in claim 8 wherein a backup plate is provided against which the sleeve becomes folded upon winding of the cables.
10. The system as claimed in claim 9 further comprising a slidable door adapted to close an opening in the building through which the sleeve is folded by the winch system(s).
11. The system as claimed in claim 2 wherein the eyelets are swivably mounted to their respective rigid support members.
12. The system as claimed in claim 1 further comprising means for forming at least one knee-like section of the sleeve in the unfolded state thereof.
13. The system as claimed in claim 12 wherein the knee-like section forming means comprise a stretch of cable tied between selected eyelets located at the top of the sleeve, the length of the cable being less than the distance between the eyelets when the sleeve is unfolded.
14. The system as claimed in claim 1 further comprising auxiliary cables adapted to be anchored to stationary objects at ground level for stabilizing the sleeve in its unfolded state.
15. The system as claimed in claim 14 wherein the auxiliary cables are connected to selected ones of the rigid support members, at two diametrically opposite sides thereof in a horizontal plane.
16. The system as claimed in claim 15 wherein the auxiliary cables are constituted by loops passed through respective rings mounted to the rigid support member(s).
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A memory system, comprising:
a central processing unit (CPU);
a nonvolatile flash memory electrically coupled in the memory system to communicate with said CPU; and
a main memory configured to swap an incoming code page read from a nonvolatile non-flash memory for a target code page therein, in response to a first command issued by said CPU;
wherein said main memory is configured to swap the target code page in said main memory to said nonvolatile flash memory in the event a page capacity of said main memory is at a threshold capacity; and
wherein said main memory includes a page table configured to maintain refault bit values therein, which indicate for each of a plurality of code pages stored in said main memory how many times the corresponding code pages have been discarded from said main memory without being written into said nonvolatile flash memory.
2. The memory system of claim 1, wherein said CPU is configured to perform a frequency of use analysis on the target code page by accessing the page table to determine whether the target code page is to be swapped into said nonvolatile flash memory or discarded because the corresponding refault bit value indicates an insufficient number of prior discards associated with the target code page.
3. The memory system of claim 1, wherein the nonvolatile non-flash memory is a disk drive storage device.
4. A memory system, comprising:
a CPU;
a nonvolatile memory configured to directly exchange data with the CPU; and
a main memory configured to store data loaded from a disk and the nonvolatile memory in response to operation of the CPU;
wherein the nonvolatile memory is used as a swap device of the main memory;
wherein the CPU swaps a code page selected as a replacing target to the nonvolatile memory from the main memory; and
wherein said main memory includes a page table configured to maintain refault bit values therein, which indicate for each of a plurality of code pages stored in said main memory how many times the corresponding code pages have been discarded from said main memory without being written into said nonvolatile memory.
5. The memory system of claim 4, wherein the CPU selects a replacing target according to a Least Recently Used (LRU) policy.
6. A method of operating a memory system containing a volatile main memory, a nonvolatile flash memory and a nonvolatile disk drive memory therein, said method comprising:
swapping a first incoming code page read from the disk drive memory for a target code page within the main memory, in response to a first CPU command, said main memory containing a page table configured to maintain refault bit values therein, which indicate for each of a plurality of code pages stored in the main memory, including the target code page, how many times each corresponding code page has been discarded from the main memory without being written into the flash memory; and
swapping a second incoming code page read from the disk drive memory for the first incoming code page within the main memory, in response to a second CPU command, by evaluating a first refault bit value associated with the first incoming code page and then either: (i) discarding the first incoming code page from the main memory upon determining that the first refault bit value has a magnitude less than a predetermined threshold, or (ii) transferring the first incoming code page from the main memory to the flash memory upon determining that the first refault bit value has a magnitude at or greater than the predetermined threshold.