From owner-freebsd-net@FreeBSD.ORG  Wed Mar 25 14:03:59 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A4ACE4E2
 for <freebsd-net@freebsd.org>; Wed, 25 Mar 2015 14:03:59 +0000 (UTC)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com
 [IPv6:2a00:1450:4010:c04::229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 252878D0
 for <freebsd-net@freebsd.org>; Wed, 25 Mar 2015 14:03:59 +0000 (UTC)
Received: by lbbsy1 with SMTP id sy1so18271704lbb.1
 for <freebsd-net@freebsd.org>; Wed, 25 Mar 2015 07:03:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=WfShH0V1W1Lu+NG3c4wjNmq/KceQgsGP6T2pYwcVNUk=;
 b=RsZLFenhLxJwEos8vBYCk+9zCqqf1KA6gy5dOtHRtehw9uUkHT5qEDTvKUylZlSD+7
 xSNBdXopCFUrQsBzS3rYqzNPcbAgf7g/sd0VF/pRtLFbX/9QcF3kbgL/mfviWOVSCMHq
 g4uxb32pXPcovM/odr2KlWGBFEQQVNi9VFGzbLX3ycbshGOjR9NQOzG/p1YLUakdW85+
 o9hHAHax3R+RjWd/Z0AYjgPxmekC4YYCnQwy3JG+yXswtSCLFXUTaDtKS10dNpIGzRM4
 oRf6PxyNcjZ0o2ZAeaXqJLUx3NzKt15SQXkDP+iUZShujnC72epxBGX4Q/a6nYNWFCLr
 5Tiw==
MIME-Version: 1.0
X-Received: by 10.152.1.70 with SMTP id 6mr8581124lak.83.1427292237058; Wed,
 25 Mar 2015 07:03:57 -0700 (PDT)
Sender: rizzo.unipi@gmail.com
Received: by 10.114.180.4 with HTTP; Wed, 25 Mar 2015 07:03:56 -0700 (PDT)
In-Reply-To: <5512BED2.2060509@gmail.com>
References: <5512BED2.2060509@gmail.com>
Date: Wed, 25 Mar 2015 15:03:56 +0100
X-Google-Sender-Auth: BmcOgbka8fJsOCIfPL-kPfmxue0
Message-ID: <CA+hQ2+jrsUP3avtNyYR8rogq7YvYAc4gt00jRksSn6pSaxzbHg@mail.gmail.com>
Subject: Re: Equivalnet options between pf_ring and netmap
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: "C.L. Martinez" <carlopmart@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2015 14:03:59 -0000

On Wed, Mar 25, 2015 at 2:57 PM, C.L. Martinez <carlopmart@gmail.com> wrote:
> Hi all,
>
>  I am trying to configure some values in netmap under a FreeBSD 10.1 host
> like it can be done with pf_ring in linux.
>
>  According to netmap(4) manual page exists some options using sysctl. But I
> am searching about these options: enable_tx_capture and min_num_slots like
> in pf_ring. Exists some equivalence in netmap? Is it posible to disable TX?
>

perhaps it is easier to tell if you explain what those pf_ring options do.
i am puzzled by the question on disabling tx,  because if you do not
want to transmit, you just... don't! :)

cheers
luigi