From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH RESEND dlm-next 0/2] fs: dlm: add support to set skb mark value
Date: Tue, 16 Jun 2020 13:47:25 -0400 [thread overview]
Message-ID: <20200616174727.34030-1-aahringo@redhat.com> (raw)
Hi,
this patch series adds support for setting the skb mark value as socket
option. It's not possible yet to change this after the socket is
created, although the mark value can be changed afterwards.
How to test it:
1. Setup mark values
echo 0xcafe > /sys/kernel/config/dlm/cluster/mark
echo 0xbeef > /sys/kernel/config/dlm/cluster/comms/2/mark
Note: setting a mark value for local node has no effect.
2. Add some skb mark classifier:
tc qdisc add dev $DEV root handle 1: htb
tc filter add dev $DEV parent 1: u32 match mark 0xcafe 0xffffffff action ok
tc filter add dev $DEV parent 1: u32 match mark 0xbeef 0xffffffff action ok
3. Mount e.g. gfs2
4. dump stats:
tc -s -d filter show dev $DEV
5. Open e.g. wireshark and check the success rate of stats
I have also patches for dlm user space to set these values via
dlm controld.
- Alex
RESEND the whole series because I don't see them in the archive,
I think because I wasn't subscribed before.
Alexander Aring (2):
fs: dlm: set skb mark for listen socket
fs: dlm: set skb mark per peer socket
fs/dlm/config.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
fs/dlm/config.h | 2 ++
fs/dlm/lowcomms.c | 40 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 86 insertions(+)
--
2.26.2
next reply other threads:[~2020-06-16 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 17:47 Alexander Aring [this message]
2020-06-16 17:47 ` [Cluster-devel] [PATCH RESEND dlm-next 1/2] fs: dlm: set skb mark for listen socket Alexander Aring
2020-06-16 17:47 ` [Cluster-devel] [PATCH RESEND dlm-next 2/2] fs: dlm: set skb mark per peer socket Alexander Aring
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=20200616174727.34030-1-aahringo@redhat.com \
--to=aahringo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).