Introduced the frandom module

Frandom is a Linux kernel random number generator,
which is 10-50 times faster than what you get from Linux'
built-in /dev/urandom. And it uses very little (/dev/frandom)
or none (/dev/erandom) of the kernel's entropy pool,
so it is very useful for applications that require a
handy source for lots of random data.

The test-results i get are quite good:

time head -c 10m /dev/urandom > /dev/null
0m4.84s real

time head -c 10 /dev/frandom > /dev/null
0m1.39s real

Just edit /etc/init.d/30rngd. Modifiy the command to this:
rngd -r /dev/frandom

Signed-off-by: Tony Liu <fentensoft@163.com>
Proportional Rate Reduction for TCP

This patch implements Proportional Rate Reduction (PRR) for TCP.
PRR is an algorithm that determines TCP's sending rate in fast
recovery. PRR avoids excessive window reductions and aims for
the actual congestion window size at the end of recovery to be as
close as possible to the window determined by the congestion control
algorithm. PRR also improves accuracy of the amount of data sent
during loss recovery.

The patch implements the recommended flavor of PRR called PRR-SSRB
(Proportional rate reduction with slow start reduction bound) and
replaces the existing rate halving algorithm. PRR improves upon the
existing Linux fast recovery under a number of conditions including:
  1) burst losses where the losses implicitly reduce the amount of
outstanding data (pipe) below the ssthresh value selected by the
congestion control algorithm and,
  2) losses near the end of short flows where application runs out of
data to send.

As an example, with the existing rate halving implementation a single
loss event can cause a connection carrying short Web transactions to
go into the slow start mode after the recovery. This is because during
recovery Linux pulls the congestion window down to packets_in_flight+1
on every ACK. A short Web response often runs out of new data to send
and its pipe reduces to zero by the end of recovery when all its packets
are drained from the network. Subsequent HTTP responses using the same
connection will have to slow start to raise cwnd to ssthresh. PRR on
the other hand aims for the cwnd to be as close as possible to ssthresh
by the end of recovery.
arm/crypto: Add optimized AES and SHA1 routines
arm: spinlock: use ticket algorithm for ARMv6+ locking implementation
Fix a kconfig warning
Fix qtouch_ratelimit kconfig

Signed-off-by: Tony Liu <fentensoft@163.com>
Fix lowmemorykiller to prevent reclaim swap
Tweak code

Signed-off-by: Tony Liu <fentensoft@163.com>
Update New config