From owner-freebsd-arch@FreeBSD.ORG Sun Dec 16 16:48:13 2007 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 532E216A46B for ; Sun, 16 Dec 2007 16:48:13 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 1A91C13C47E for ; Sun, 16 Dec 2007 16:48:12 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so2892285waf.3 for ; Sun, 16 Dec 2007 08:48:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=M+luHTHa4aZzvs4dmrQPPg9kISIClW557vjs7as9RTw=; b=QKIem97MmBwu+9gpPvikalRU4QABM33yomTS+d6TwufptvPA3p98pT/MDM/g2lkDT3cQOtm2dz3xRRHMaWnZLPvnlXc1T/58wAtVyjwzS/JwxVOyNLv5DZi+RaJFHf6IF8fCHfe9Lrh3excjYIO7G7K4XYQXTap67F2vEtbc2m8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=itykqsxvQAVn7wMpevuoS7FKCqIr3rNQXLK5bCgUtJJShQ/E+Pt9Ac968aXa2x1Cj2gPwnXYStzpCLSl1FLaYip7zTLoG0jOtbD0lkErLSPMwmsO0KyIY1Golt/3kLo+jBMsObLaSjO7xgzebJSXn6QQWWWCGS+2MpFk+Bmklko= Received: by 10.114.120.1 with SMTP id s1mr2234300wac.107.1197823692718; Sun, 16 Dec 2007 08:48:12 -0800 (PST) Received: by 10.114.255.11 with HTTP; Sun, 16 Dec 2007 08:48:12 -0800 (PST) Message-ID: Date: Sun, 16 Dec 2007 08:48:12 -0800 From: "Kip Macy" To: "Robert Watson" , "Sam Leffler" , freebsd-arch@freebsd.org, "FreeBSD Current" In-Reply-To: <20071216111315.C49036@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071215100351.Q70617@fledge.watson.org> <20071216111315.C49036@fledge.watson.org> Cc: Subject: Re: pending changes for TOE support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 16:48:13 -0000 Reset is fine, given that internally it just calls t3_send_reset. On 12/16/07, Robert Watson wrote: > > On Sat, 15 Dec 2007, Kip Macy wrote: > > >> + * + tu_abort > >> + * - closes the connection and sends a RST to peer > >> + * - driver is expectd to trigger an RST and detach the toepcb > >> > >> In regular TCP, the pru_abort method is only called on pending > connections > >> while still in the listen queues of a listen socket. Is this true of > >> tu_abort, or is tu_abort a more general method to be used to cancel > >> connections? If so, probably worth commenting on that. > > > > tu_abort is called in place of tcp_output in pru_abort. > > The reason I ask is that it appears tu_abort appears to be the only > interface > allowing the stack to request that TOE reset of a connection. In regular > TCP, > soabort/pru_abort/tcp_usr_abort are used only on nascent unaccepted > connections; at least one other path, used by tcpdrop(8), can lead to > connections being reset as well. Perhaps a more general tu_reset could be > used to address this? I'm not sure what other direct-to-reset paths exist > but > a review for them may be called for. > > Robert N M Watson > Computer Laboratory > University of Cambridge >