netdev - Re: [PATCHSET 0/18] FRTO: fixes and small changes + SACK enhanced version

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 22 Feb 2007 05:33:58 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ilpo.jarvinen@...sinki.fi
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCHSET 0/18] FRTO: fixes and small changes + SACK enhanced
 version

From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Thu, 22 Feb 2007 14:25:32 +0200 (EET)

> Before preparing the submittable spurious RTO responses patch, I would 
> like to know what is the preferred style for the response selector code 
> (I'm controlling the response through frto_response sysctl)? switch? array 
> of function pointers? If array, where to place it (considering the need 
> for forward declarations and mixing of code and data in some approaches)?

If it's just in the FRTO paths and controlled by sysctl, and the number
of cases are relatively small, just a set of if() tests or a
switch() statement would work fine.
-
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