From owner-freebsd-net@freebsd.org Mon Jan 18 14:08:17 2016 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 5F8C1A878FB for ; Mon, 18 Jan 2016 14:08:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 469C5176E for ; Mon, 18 Jan 2016 14:08:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 413D5A878F8; Mon, 18 Jan 2016 14:08:17 +0000 (UTC) Delivered-To: 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 40946A878F6; Mon, 18 Jan 2016 14:08:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2198176C; Mon, 18 Jan 2016 14:08:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u0IE8CrR054635 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 18 Jan 2016 16:08:12 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u0IE8CrR054635 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u0IE8Boc054634; Mon, 18 Jan 2016 16:08:11 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 18 Jan 2016 16:08:11 +0200 From: Konstantin Belousov To: Boris Astardzhiev Cc: Jilles Tjoelker , net@freebsd.org, threads@freebsd.org Subject: Re: Does FreeBSD have sendmmsg or recvmmsg system calls? Message-ID: <20160118140811.GW3942@kib.kiev.ua> References: <20160108204606.G2420@besplex.bde.org> <20160113080349.GC72455@kib.kiev.ua> <20160116195657.GJ3942@kib.kiev.ua> <20160116202534.GK3942@kib.kiev.ua> <20160117211853.GA37847@stack.nl> <20160118044826.GS3942@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2016 14:08:17 -0000 On Mon, Jan 18, 2016 at 12:37:01PM +0200, Boris Astardzhiev wrote: > Hello, > > Sorry for the delay of my reply. As far as I understand pthread_testcancel() > is not necessary in the recvmmsg syscall since cancellation is not quite > common > among apps. But if there is cancellation attempts as long as I use > __sys_recvmsg() instead > of the interposing approach on a cancel attempt recvmmsg() will return > EINTR which will get > me out? Yes. The corner case is the cancellation attempt (SIGCANCEL == SIGTHR) coming while the thread is executing code around the syscall. > > Secondly, I guess it's better to use __sys_sendmmsg() similarly instead of > the > insterposing table regarding sendmmsg(). Sure, sendmmsg and recvmmsg are same. > > Lastly, regarding the manpage - should I extend send/recv(2) for the new > calls or > create new manpage files? IMO it is more logical to extend the existing page than write a new one.