From owner-freebsd-net@freebsd.org Fri Apr 7 13:15:54 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0B03D307A8 for ; Fri, 7 Apr 2017 13:15:54 +0000 (UTC) (envelope-from lukasz.wojcik@zoho.com) Received: from sender-pp-091.zoho.com (sender-pp-091.zoho.com [135.84.80.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 97A64F8C for ; Fri, 7 Apr 2017 13:15:54 +0000 (UTC) (envelope-from lukasz.wojcik@zoho.com) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:to:references:from:message-id:date:user-agent:mime-version:in-reply-to:content-type; b=QQLnce4BjcmEdt9E0D4MxsHTJm1QKQEfdsLPdE6T6/LvpAlivCE3nXgu0P2iM5qKbRBIxyRnaleH +4Tk+CpClrCKK4+sF4E4rz/1vXcbsHo+ne7gckWchiesf4oPfos2 Received: from [192.168.1.102] (91.200.105.117 [91.200.105.117]) by mx.zohomail.com with SMTPS id 149157095139735.60021628282311; Fri, 7 Apr 2017 06:15:51 -0700 (PDT) Subject: Re: Impending NATM removal To: freebsd-net@freebsd.org References: <20170406235747.GA8756@spindle.one-eyed-alien.net> From: =?UTF-8?B?xYF1a2FzeiBXw7NqY2lr?= Message-ID: Date: Fri, 7 Apr 2017 15:15:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-ZohoMailClient: External X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 13:15:54 -0000 Oh, and mbpool DMA syncing does not work at all and -- at least in patm driver -- causes various issues. This of course can be easily worked around if you choose to let ATM ecosystem stay. If my client agrees, I could also share a patch for patm to make it work with newer ProSUM hardware. -ŁW On 07-Apr-17 15:08, Łukasz Wójcik wrote: > Hi Brooks, > > > AFAIK Prosum still manufactures PROATM155M card that utilizes patm > driver (which is by the way a little bit outdated and does > > not support newer variants of ProSUM cards). I also have clients that > still use ATM and prosum cards and FreeBSD. My guess is that > > they're not the only ones. Just my 5cents. The other thing is that > ATM/NATM infrastructure in FreeBSD seems to never have been > > finished. > > > Thanks > > -ŁW > > > On 07-Apr-17 01:57, Brooks Davis wrote: >> As previously threatened, I plan to remove NATM support next week. This >> includes the drivers en(4), fatm(4), hatm(4), and patm(4). None of >> these devices have been manufactured in the last 20 years so it is time >> to move on. >> >> The planned commit can be seen at https://reviews.freebsd.org/D9883 >> >> -- Brooks > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"