From owner-soc-status@freebsd.org Wed Jul 18 19:35:23 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B13ED102F8EA for ; Wed, 18 Jul 2018 19:35:23 +0000 (UTC) (envelope-from duostefano93@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 1AEF789A1B for ; Wed, 18 Jul 2018 19:35:23 +0000 (UTC) (envelope-from duostefano93@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id q20-v6so5995351ith.0 for ; Wed, 18 Jul 2018 12:35:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=8ThaNRHtkJ6o8ZHE54IQcMpIpSquH8mB0vWo8XINY/o=; b=ik9lkILGknNEbYDRiI5VxBI9xQRu3JsA+xqAe8vHZweKHy3EIMr8/U/oRmoYLXmkTK uAJZI5/h2kUP7LtuzqY08QBmlIq2xFmgnPA8+hHePj/hSzQova4urI9x0832T/QBSATA cblFK+xiilaoaQzlE7BIxfEM0EmFGdv1ruMomAIfRwEpWTig/OsAa95JM6w9vnZeiaRJ OEdvP5cThEsQuCTqmQNDw+MVvX6uIEAV4xJyfeNfDYmnCvQI2Ck6WFxL4WvX4G9sIV5/ VmUXjzYtphyqkssn/JvSU/kUJ0htKGALpi1MLqGInB6FMPQ0k3lg3ZOQLrCirG74CQ8+ +wZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=8ThaNRHtkJ6o8ZHE54IQcMpIpSquH8mB0vWo8XINY/o=; b=ix2BK5xub0kHqy93DEbaldcZCUYepVhpkK0so4uOqkUrzKLZRAll2k0Zdodk/5w4f+ h/nRXQRoR7Ahszcjwet5rmt74XHgw7tt6muIuPyX9X0xdkMy6OHYwh7Blw7ADOtSohjy 1SrFE9Nt+AdCt2s9SgOVynq3EdFWyteA4ieULOb60lzYzjDjS++LHIpAQNup9HyIaJJY af1HVpoiNpsuAbcCm++bBVwdRo+030ja4oR9bE8RGL2BhmerKNbbUzXHGMKS9aNibmrJ DxI1V9XnE6jH/3bRG50zs6MSMxNTA8LwtNQfSYuy1bWY9dGxIfYfDhIxybiNLiKvvpcm pCSQ== X-Gm-Message-State: AOUpUlGHl1Ft4GA0AEpX93vkGyY24I/UcfB03DtkQt38YIAxqkisNBsh 2+L/5tdVgHtIVRptnR3W5oXQ1ixrNq4OYs/Ji1DauA== X-Google-Smtp-Source: AAOMgpebaTB81ndBBY6BOwTrbmM+Tk0t8L4u20hZBAnrLI0kgzfk/AMueNTwqsvyxZww1w1ZbPe9WrdVYIbBulgb1gk= X-Received: by 2002:a24:57cc:: with SMTP id u195-v6mr3171898ita.142.1531942522197; Wed, 18 Jul 2018 12:35:22 -0700 (PDT) MIME-Version: 1.0 From: Stefano Duo Date: Wed, 18 Jul 2018 21:35:10 +0200 Message-ID: Subject: Extensions to the netmap framework - Week 9 To: soc-status@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2018 19:35:24 -0000 Hi, during this past week i added support for per-ring fixed offsets. The library net/netmap_user.h has been changed accordingly and applications will automatically handle the offsets through the NETMAP_BUF() macro after being re-compiled. This type of offset can be specified during a NETMAP_REQ_REGISTER command by adding a struct nmreq_opt_ring_offset to the option list. The offset will be applied to each ring specified by the register request with the exception of netmap pipes and monitors: - netmap pipes apply the offset to every ring of both ends, regardless of the specified rings. - netmap monitors retrieve the offset from the monitored rings, therefore it is considered an error if an application specifies an offset during the register command, or if the specified rings to monitor have been registered with different offsets. Project wiki: https://wiki.freebsd.org/SummerOfCode2018Projects/ExtensionsToNetmap SVN repository: https://svnweb.freebsd.org/socsvn/soc2018/sduo/ Stefano.