From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id D5DC02B53C for ; Thu, 11 Apr 2019 19:11:26 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgM2aF5Rr_mo for ; Thu, 11 Apr 2019 19:11:26 -0400 (EDT) Received: from smtp61.i.mail.ru (smtp61.i.mail.ru [217.69.128.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 8537929A00 for ; Thu, 11 Apr 2019 19:11:26 -0400 (EDT) Date: Fri, 12 Apr 2019 02:11:24 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH 4/6] test: generalize SWIM fake descriptor filters Message-ID: <20190411231124.GF31339@chai> References: <1f85ec77d0a00f844d3d273fb6b138845e7e8917.1555021137.git.v.shpilevoy@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1f85ec77d0a00f844d3d273fb6b138845e7e8917.1555021137.git.v.shpilevoy@tarantool.org> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Vladislav Shpilevoy Cc: tarantool-patches@freelists.org * Vladislav Shpilevoy [19/04/12 01:25]: > At this moment SWIM test harness implementes its own fake file > descriptor table, which is used unawares by the real SWIM code. > Each fake fd has send and recv queues, can delay and drop > packets with a certain probability. But it is going to be not > enough for new tests. > > It is wanted to be able to drop packets with a specified content, > from and to a specified direction. For that the patch implements > a filtering mechanism. Each fake fd now has a list of filters, > applied one by one to each packet. If at least on filter wants to > drop a packet, then it is dropped. The filters know packet > content and direction: outgoing or incomming. > > Now only one filter exists - drop rate. It existed even before > the patch, but now it is ported on the new API. ok to push. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov