From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>,
"Marek Lindner" <mareklindner@neomailbox.ch>
Subject: Re: [PATCH v2] batman-adv: Introduce no noflood mark
Date: Tue, 07 May 2019 17:45:04 +0200 [thread overview]
Message-ID: <8751913.vGonOqSknk@bentobox> (raw)
In-Reply-To: <20190507151723.GB1493@otheros>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Tuesday, 7 May 2019 17:17:23 CEST Linus Lüssing wrote:
> Ah, that's an interesting idea. So basically filtering on the
> hardif instead of in batman-adv via some custom compiled BPF
> filters. So basically similar to writing a small program like the
> gluon-radv-filterd with a BPF_* parser?
>
> https://github.com/freifunk-gluon/gluon/blob/master/package/gluon-radv-filterd/src/gluon-radv-filterd.c#L223
Yes, but you don't have to write the stuff with these intrinsics and cBPF.
This was done in gluon-radv-filterd only to avoid extra dependencies to
build the program for this really minimal piece of code.
And I didn't had much benefits from using eBPF at the moment [1].
You can just write it in C and use clang to create (e)BPF bytecode as
described in http://man7.org/linux/man-pages/man8/tc-bpf.8.html
Kind regards,
Sven
[1] https://github.com/freifunk-gluon/gluon/pull/838#issuecomment-355547594
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-07 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 7:28 [PATCH v2] batman-adv: Introduce no noflood mark Linus Lüssing
2019-05-07 7:30 ` Sven Eckelmann
2019-05-07 8:00 ` Marek Lindner
2019-05-07 8:21 ` Sven Eckelmann
2019-05-07 15:17 ` Linus Lüssing
2019-05-07 15:34 ` Linus Lüssing
2019-05-07 15:45 ` Sven Eckelmann [this message]
2019-05-14 8:19 ` Linus Lüssing
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8751913.vGonOqSknk@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
--cc=mareklindner@neomailbox.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.