netdev - Re: [PATCH 2/3] Seperate DSACK from SACK fast path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20070204.233658.130236812.davem@davemloft.net>
Date:	Sun, 04 Feb 2007 23:36:58 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	baruch@...en.org
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 2/3] Seperate DSACK from SACK fast path

From: Baruch Even <baruch@...en.org>
Date: Fri, 02 Feb 2007 16:41:21 +0200

> Move DSACK code outside the SACK fast-path checking code. If the DSACK
> determined that the information was too old we stayed with a partial cache
> copied. Most likely this matters very little since the next packet will not be
> DSACK and we will find it in the cache. but it's still not good form and there
> is little reason to couple the two checks.
> 
> Since the SACK receive cache doesn't need the data to be in host order we also
> remove the ntohl in the checking loop.
> 
> Signed-Off-By: Baruch Even <baruch@...en.org>

Thanks for fixing up the endianness annotations, applied.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html