Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: [PATCH bpf-next 0/3] Implement bpf map queue
Date: Mon, 6 Aug 2018 18:58:07 -0700	[thread overview]
Message-ID: <CAA93jw7Y71Ghs1Frt2RRx7zeyUgfXzYZWLFfiTLtSRe3BQ+T1w@mail.gmail.com> (raw)
In-Reply-To: <153356387977.6981.12236150594041620482.stgit@kernel>

I think I have a new aphorism.

The size of any hardware oriented language grows until it can support
an infinite fifo queue.

---------- Forwarded message ---------
From: Mauricio Vasquez B <mauricio.vasquez@polito.it>
Date: Mon, Aug 6, 2018 at 8:09 AM
Subject: [PATCH bpf-next 0/3] Implement bpf map queue
To: Alexei Starovoitov <ast@kernel.org>, Daniel Borkmann <daniel@iogearbox.net>
Cc: <netdev@vger.kernel.org>


Bpf queue map is a new kind of map that provides a LIFO/FIFO queue
implementation.

In some applications, like a SNAT, it is necessary to keep track of
a pool of free elemenets, network ports in this case, then a queue
can be used for that purpose.

Signed-off-by: Mauricio Vasquez B <mauricio.vasquez@polito.it>
---
Mauricio Vasquez B (3):
      bpf: add bpf queue map
      selftests/bpf: add test cases for BPF_MAP_TYPE_QUEUE
      bpf: add sample for BPF_MAP_TYPE_QUEUE


 include/linux/bpf_types.h               |    1
 include/uapi/linux/bpf.h                |    5 +
 kernel/bpf/Makefile                     |    2
 kernel/bpf/queuemap.c                   |  287 +++++++++++++++++++++++++++++++
 kernel/bpf/syscall.c                    |   61 +++++--
 kernel/bpf/verifier.c                   |   16 +-
 samples/bpf/.gitignore                  |    1
 samples/bpf/Makefile                    |    3
 samples/bpf/test_map_in_map_user.c      |    9 -
 samples/bpf/test_queuemap.sh            |   37 ++++
 samples/bpf/test_queuemap_kern.c        |   51 ++++++
 samples/bpf/test_queuemap_user.c        |   53 ++++++
 tools/include/uapi/linux/bpf.h          |    5 +
 tools/testing/selftests/bpf/test_maps.c |   72 ++++++++
 14 files changed, 577 insertions(+), 26 deletions(-)
 create mode 100644 kernel/bpf/queuemap.c
 create mode 100755 samples/bpf/test_queuemap.sh
 create mode 100644 samples/bpf/test_queuemap_kern.c
 create mode 100644 samples/bpf/test_queuemap_user.c

--



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

           reply	other threads:[~2018-08-07  1:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <153356387977.6981.12236150594041620482.stgit@kernel>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7Y71Ghs1Frt2RRx7zeyUgfXzYZWLFfiTLtSRe3BQ+T1w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox