Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository

Switch branch/tag
  • xcap-capability-linux
  • net
  • ipv4
  • tcp_input.c
Find file BlameHistoryPermalink
  • Baruch Even's avatar
    [TCP]: Check num sacks in SACK fast path · 8a3c3a97
    Baruch Even authored Feb 04, 2007
    
    
    We clear the unused parts of the SACK cache, This prevents us from mistakenly
    taking the cache data if the old data in the SACK cache is the same as the data
    in the SACK block. This assumes that we never receive an empty SACK block with
    start and end both at zero.
    Signed-off-by: default avatarBaruch Even <baruch@ev-en.org>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    8a3c3a97

Replace tcp_input.c

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.