From owner-freebsd-arch@FreeBSD.ORG Tue Jul 15 10:52:33 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4981BF5C for ; Tue, 15 Jul 2014 10:52:33 +0000 (UTC) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3ED3288A for ; Tue, 15 Jul 2014 10:52:32 +0000 (UTC) Received: by mail-la0-f49.google.com with SMTP id gf5so3866013lab.36 for ; Tue, 15 Jul 2014 03:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Z8+tSRFKpEXndKLxsfnliUOYcpPSwtVa7iKoK+wS/nk=; b=K74y8cQjkI0CwG/bnJ1nVK3431ZkT+m/yu0P2I7CZ9p2Oe5tXc67doxbbw+Cyt5qXF HeJN0jNtDmxu1CV+3YU5kZ3pQ8P2XlnEcdiB7pKmjdvHtVETEmbPnX1kSOi2nwB2LEiD 5BG5rCL85lSBNvSQiEcGqu1uhlm3JFqJc2vpoJa0rNptHIJnFRFlh5gHfT9CMjgogGYA aeJT3M6PtyTtInFIw9wbvqk/jbk4YtVSSmsRkAXEQXduf5MqoGgpBGvgS2rDkjWwrp2j bCcKoNNJBFUYtWn9n1VWvrN8J7FK08uJ1s3NLh2ca82LqlN6y4ytjDW46rP2Yu85j6WH aOOg== X-Received: by 10.112.235.72 with SMTP id uk8mr1529271lbc.80.1405421550429; Tue, 15 Jul 2014 03:52:30 -0700 (PDT) Received: from [192.168.2.30] ([2.176.190.226]) by mx.google.com with ESMTPSA id as6sm19679335lbc.31.2014.07.15.03.52.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jul 2014 03:52:29 -0700 (PDT) Message-ID: <53C507F2.2090604@gmail.com> Date: Tue, 15 Jul 2014 15:22:34 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Slawa Olhovchenkov Subject: Re: UDP/TCP versus IP frames - subtle out of order packets with hardware hashing References: <53C4EE00.5090705@gmail.com> <20140715093125.GA89128@zxy.spb.ru> In-Reply-To: <20140715093125.GA89128@zxy.spb.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2014 10:52:33 -0000 On 7/15/2014 2:01 PM, Slawa Olhovchenkov wrote: > On Tue, Jul 15, 2014 at 01:31:52PM +0430, Hooman Fazaeli wrote: > >> Doesn't the problem applies to TCP too? >> TCP may be fragmented too but is less likely because of MSS. > Don't forget GRE, IPIP, ESP and AH! > These protocols don't use port numbers and the RSS hash is computed based on the (srcip,dstip) tuple, so the problem does not apply to them. -- Best regards. Hooman Fazaeli