cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH dlm/next 0/6] fs: dlm: rework receive and transmit handling
Date: Fri, 18 Sep 2020 10:27:22 -0400	[thread overview]
Message-ID: <20200918142728.147392-1-aahringo@redhat.com> (raw)

Hi,

This patch series contains a huge change regarding to the
receive/transmit handling of dlm. As I placed sequence numbering on dlm
messages I expierenced that dlm messages can be transmitted in an
incorrect order. I changed the transmit handling that the writequeue
handles entries per dlm message buffer and sendmsg() will use
scatter/gather to transmit a bunch of them. At the receive handling I
removed some allocations and copies into different buffers. There is
only one receive buffer now which fill be get filled and the upper layer
will working on that buffer as well.

- Alex

Alexander Aring (6):
  fs: dlm: remove lock dependency warning
  fs: dlm: handle range check as callback
  fs: dlm: disallow buffer size below default
  fs: dlm: release connection with call_rcu
  fs: dlm: rework receive handling
  fs: dlm: rework transmit handling

 fs/dlm/config.c   |  47 +++--
 fs/dlm/config.h   |   2 +
 fs/dlm/lowcomms.c | 471 ++++++++++++++++++++++------------------------
 fs/dlm/midcomms.c | 136 ++++++-------
 fs/dlm/midcomms.h |   3 +-
 5 files changed, 310 insertions(+), 349 deletions(-)

-- 
2.26.2



             reply	other threads:[~2020-09-18 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 14:27 Alexander Aring [this message]
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 1/6] fs: dlm: remove lock dependency warning Alexander Aring
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 2/6] fs: dlm: handle range check as callback Alexander Aring
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 3/6] fs: dlm: disallow buffer size below default Alexander Aring
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 4/6] fs: dlm: release connection with call_rcu Alexander Aring
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 5/6] fs: dlm: rework receive handling Alexander Aring
2020-09-18 14:27 ` [Cluster-devel] [PATCH dlm/next 6/6] fs: dlm: rework transmit handling Alexander Aring
2020-09-22 20:52 ` [Cluster-devel] [PATCH dlm/next 0/6] fs: dlm: rework receive and " Alexander Ahring Oder 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=20200918142728.147392-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).