From: piaojun <piaojun@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC PATCH 0/5] ocfs2: support IPv6 communication in o2cb cluster
Date: Thu, 8 Nov 2018 09:57:28 +0800 [thread overview]
Message-ID: <5BE39808.5080205@huawei.com> (raw)
In-Reply-To: <20181107145654.151723a2fe9a44e9c7e3a8de@linux-foundation.org>
Hi Andrew,
On 2018/11/8 6:56, Andrew Morton wrote:
> On Thu, 25 Oct 2018 18:31:15 +0800 piaojun <piaojun@huawei.com> wrote:
>
>> o2cb cluster only support IPv4 node configuration nowadays. Along with IPv6
>> used more widely, ocfs2 should also keep up with the pace. This patch
>> series add configfs attribute for IPv6 configure and build connnection
>> between nodes with IPv6 socket. So the nodes in cluster could send dlm
>> messages through IPv6 network protocol.
>
> Big patchset. I'll await some reviewer input before looking at merging
> this, I think.
>
> Please update Documentation/filesystems/ocfs2.txt to document all the
> new userspace interfaces and the overall feature, etc.
OK, there is some work in userspace, such as o2cb_ctl, and I will add
another patch to update the document.
>
> Should the new code be hidden behind `#ifdef CONFIG_IPV6'? That would
> avoid some code bloat.
>
> (That being said, if ocfs2 was concerned about code bloat, it would do
> something about the fact that mlog() and mlog_errno() more than double
> the file system's object code size).
Good suggestion, and I will consider using CONFIG_IPV6 to make code
thiner.
Thanks,
Jun
>
> .
>
prev parent reply other threads:[~2018-11-08 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 10:31 [Ocfs2-devel] [RFC PATCH 0/5] ocfs2: support IPv6 communication in o2cb cluster piaojun
2018-11-07 22:56 ` Andrew Morton
2018-11-08 1:57 ` piaojun [this message]
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=5BE39808.5080205@huawei.com \
--to=piaojun@huawei.com \
--cc=ocfs2-devel@oss.oracle.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 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.