Forgot your password?
typodupeerror

Comment Re:Compiling the kernel (Score 1) 603

laffer1 wrote: "This helps if there is a crazy background process eating up CPU and it might even help control flash crushing system performance a bit."

Well, sort of, but not really. A competent video player is fine running along with CPU intensive background processes. The problem is competing for attention with new-born babies.

A parallel 'make' will fork() and exec() short-running processes at the rate of dozens per second. The scheduler will find that each new-born processes has used up zero CPU so far, and therefor put them ahead of the video player and browser, which have already sucked major CPU without completing their work.

A task group for each TTY fixes that particular problem. Each child process has to wait and share the CPU time allocated to its group. Immoral as charging children with debts of their parents may seem, in this case it smooth out our video and web browsing so that's that.

Comment Re:128 vs 256 Bit AES (Score 1) 146

Data has an "intelligence life": the period in which its exposure is harmful.
The NSA ended its Venona project not because they could recover no more
plaintext, but because the information was too dated to be of value. U.S.
Census data on individuals is seeled for 72 years; then it is public record.

Right now 72 bits is at the outer edge of what we can break exhaustively. If
we accept Moore's law as indicating that each 18 months we can take on another
bit, then 128 bits is good for 84 years.

The systems here have problems that vastly dominate the difference between
128-bit AES and 256-bit AES. Moreover, we really don't have any systems
where direct attack of 128-bit AES is the week link. 128 vs 256 Bit AES
is so far down the list of security issues that it should not occupy one
second of our attention. Doh! Too late.

Slashdot Top Deals

When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren

Working...