Prev: [GIT PULL] nilfs2 fix for 2.6.33
Next: bitops: compile time optimization for hweight_long(CONSTANT)
From: David Miller on 3 Feb 2010 12:00

Locking belongs inside of the application, not in the kernel.

As evidenced by the fact that you had to add new socket options, the
application needs to be modified anyways.

It's therefore just as easy to add the appropriate locking to the
sequences where the application writes over the TCP socket. And
it avoids having to modify the kernel at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [GIT PULL] nilfs2 fix for 2.6.33
Next: bitops: compile time optimization for hweight_long(CONSTANT)