Advanced

Performance Tradeoffs of Linux TCP SACK

Posted by IdaAshley on · Post a comment
IBM/developerWorks; By Patrick McManus 		Mail this story
Print this story

Recently there has been significant discussion of Linux's TCP SACK implementation, and its weakness within the Linux TCP stack. SACK is an optional feature of TCP necessary for effective use of all available bandwidth of some networks. However, processing this type of acknowledgment can be CPU intensive for the TCP sender, and thus a weakness which can be exploited by a malicious peer.

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: IBM, Linux

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments

No comments yet. Be the first.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post