Actually, if you set it up properly, QoS should work.
First of all, you need to combine QoS with traffic-shaping. (QoS tagging doesn't do you any good if you don't act on those tags) Second of all, you need to use that traffic-shaping to limit both the egress AND ingress BT traffic to reserve enough bandwidth for your VoIP traffic (e.g. 90% of your bandwidth, or something like that). It helps to have the type of internet connection where your bandwidth rates are constant so that it's easier to calculate how much to allow for BT traffic. The back-off algorithms in the TCP stacks will throttle back when you start dropping packets.
Anyways, it IS possible to throttle ingress traffic, but only if you're trying to throttle TCP traffic. Ingress throttling isn't quite as effective because you're on the wrong side of the bottleneck, so you might need to add a little more margin to your ingress traffic-shaping.
The reason you don't see a lot of laptop SSDs with more than 32GB is because it is still not trivial to pack that many flash chips into a 2.5" laptop disk form-factor (standard 2.5" drive in X and Y dimensions, 9.5mm in Z dimension).
When the next increment in flash capacities hits, you'll see a lot more 64GB drives and one or two vendors who can do 128GB.
I don't know where you got your info, but 'modern' flash has horrible life-expectancy in terms or write-cycles.
Explanation:
Most flash vendors have moved to MLC (Multi-Level Cell) flash. It's cheaper and denser, but the bit-error rate goes up because you have more bits per cell. The typical life expectancy for MLC is somewhere in the range of 10,000 writes using single-bit error correction. This is compared to 'older' SLC flash which has a write endurance of 100,000 to 300,000 writes.
Now, most vendors making media out of flash take varying degrees of a combination of two approaches (in addition to standard wear-leveling approaches). The first approach is to assume that the majority of the users will only ever store audio or video data so the occasional uncorrectable error won't have much impact as long as it doesn't corrupt the filesystem. The second approach is to use more advanced error correcting algorithms to compensate for the higher bit-error rate.
Using more advanced algorithms, it's possible to get more than 300,000 writes out of a MLC flash-block before the errors become uncorrectable.
P.S. I may be wrong, but I believe flash can have some really odd error conditions. For example, it's possible to disturb a bit in a block just by reading it. I believe it's also possible to disturb a bit in a different block on the same matrix when writing. That's why some form of error correction is always required with NAND flash.
It's the Army's plan for smart mines as part of their Future Combat Systems program. They can do everything this DARPA program described and more. (Including remote activation, deactivation, and detonation)
The Intelligent Munitions System (IMS) is an unattended munitions system providing both offensive battlespace shaping and defensive force protection capabilities for the Future Force. The Intelligent Munitions System (IMS) is a system of lethal and nonlethal munitions integrated with robust command and control features, communications devices, sensors and seekers that make it an integral part of the Future Combat Systems network's core systems.
Intelligent Munitions System (IMS) provides unmanned terrain dominance, economy of force and risk mitigation for the warfighting commander. Typical missions include:
* Isolating enemy forces, objectives, and areas of decisive operations.
* Creating lucrative targets, and engaging them or cueing other fires.
* Filling gaps in the noncontiguous battlespace.
* Controlling noncombatant movement with its nonlethal capabilities.
With its reduced footprint, Intelligent Munitions System (IMS) can be delivered by various means, and once on the ground, locate itself, organize all of its components and report its location to the Battle Command Mission Execution (BCME). It will be under positive control of the BCME, one of the FCS command and control applications. The munition field can be armed, turned off to allow friendly passage, then rearmed to resume its mission. This on-off-on capability allows it to be recoverable, further reducing its logistics footprint. Intelligent Munitions System (IMS) will not become a residual hazard; it will self-destruct on command or at a preset time interval. It will also be tamper resistant.
More importantly, it must be borne in mind that not all Internet users speak English as their mother tongue.
Maybe so, but how many people on the internet have never seen an american movie? It's pretty dificult to be un-aware of certain american slang terms these days.
Slashdot Mirror
Actually, if you set it up properly, QoS should work.
First of all, you need to combine QoS with traffic-shaping. (QoS tagging doesn't do you any good if you don't act on those tags) Second of all, you need to use that traffic-shaping to limit both the egress AND ingress BT traffic to reserve enough bandwidth for your VoIP traffic (e.g. 90% of your bandwidth, or something like that). It helps to have the type of internet connection where your bandwidth rates are constant so that it's easier to calculate how much to allow for BT traffic. The back-off algorithms in the TCP stacks will throttle back when you start dropping packets.
Anyways, it IS possible to throttle ingress traffic, but only if you're trying to throttle TCP traffic. Ingress throttling isn't quite as effective because you're on the wrong side of the bottleneck, so you might need to add a little more margin to your ingress traffic-shaping.
The reason you don't see a lot of laptop SSDs with more than 32GB is because it is still not trivial to pack that many flash chips into a 2.5" laptop disk form-factor (standard 2.5" drive in X and Y dimensions, 9.5mm in Z dimension).
When the next increment in flash capacities hits, you'll see a lot more 64GB drives and one or two vendors who can do 128GB.
I don't know where you got your info, but 'modern' flash has horrible life-expectancy in terms or write-cycles.
Explanation:
Most flash vendors have moved to MLC (Multi-Level Cell) flash. It's cheaper and denser, but the bit-error rate goes up because you have more bits per cell. The typical life expectancy for MLC is somewhere in the range of 10,000 writes using single-bit error correction. This is compared to 'older' SLC flash which has a write endurance of 100,000 to 300,000 writes.
Now, most vendors making media out of flash take varying degrees of a combination of two approaches (in addition to standard wear-leveling approaches). The first approach is to assume that the majority of the users will only ever store audio or video data so the occasional uncorrectable error won't have much impact as long as it doesn't corrupt the filesystem. The second approach is to use more advanced error correcting algorithms to compensate for the higher bit-error rate.
Using more advanced algorithms, it's possible to get more than 300,000 writes out of a MLC flash-block before the errors become uncorrectable.
P.S. I may be wrong, but I believe flash can have some really odd error conditions. For example, it's possible to disturb a bit in a block just by reading it. I believe it's also possible to disturb a bit in a different block on the same matrix when writing. That's why some form of error correction is always required with NAND flash.
Intelligent Munitions Systems
It's the Army's plan for smart mines as part of their Future Combat Systems program. They can do everything this DARPA program described and more. (Including remote activation, deactivation, and detonation)
Check out this text from the Army's web-site:
http://www.army.mil/fcs/factfiles/ims.html
The Intelligent Munitions System (IMS) is an unattended munitions system providing both offensive battlespace shaping and defensive force protection capabilities for the Future Force. The Intelligent Munitions System (IMS) is a system of lethal and nonlethal munitions integrated with robust command and control features, communications devices, sensors and seekers that make it an integral part of the Future Combat Systems network's core systems.
Intelligent Munitions System (IMS) provides unmanned terrain dominance, economy of force and risk mitigation for the warfighting commander. Typical missions include:
* Isolating enemy forces, objectives, and areas of decisive operations.
* Creating lucrative targets, and engaging them or cueing other fires.
* Filling gaps in the noncontiguous battlespace.
* Controlling noncombatant movement with its nonlethal capabilities.
With its reduced footprint, Intelligent Munitions System (IMS) can be delivered by various means, and once on the ground, locate itself, organize all of its components and report its location to the Battle Command Mission Execution (BCME). It will be under positive control of the BCME, one of the FCS command and control applications. The munition field can be armed, turned off to allow friendly passage, then rearmed to resume its mission. This on-off-on capability allows it to be recoverable, further reducing its logistics footprint. Intelligent Munitions System (IMS) will not become a residual hazard; it will self-destruct on command or at a preset time interval. It will also be tamper resistant.
--Cantinflas
More importantly, it must be borne in mind that not all Internet users speak English as their mother tongue.
Maybe so, but how many people on the internet have never seen an american movie? It's pretty dificult to be un-aware of certain american slang terms these days.