[LU-13308] update changelog_ext_nid to handle IPv6 addresses Created: 28/Feb/20 Updated: 07/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | Neil Brown |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | IPv6 | ||
| Issue Links: |
|
||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||
| Description |
|
In struct changelog_ext_nid there is the possibility of using a larger lnet_nidv6_t to store IPv6 NIDs. This needs to be implemented in print_changelog_rec(), lfs_changelog() to understand the larger NIDs. It seems possible to just store the larger NID therein, and check whether extra and padding are zero to distinguish between IPv4 and IPv6 addresses. It would probably make sense to use the first two __u64 for the IPv6 address, and padding for the lnet network type/number.
struct changelog_ext_nid {
/* have __u64 instead of lnet_nid_t type for use by client api */
__u64 cr_nid;
/* for use when IPv6 support is added */
__u64 extra;
__u32 padding;
};
|
| Comments |
| Comment by James A Simmons [ 14/May/23 ] |
| Comment by Gerrit Updater [ 13/Sep/23 ] |
|
"James Simmons <jsimmons@infradead.org>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/52361 |
| Comment by James A Simmons [ 17/Sep/23 ] |
|
I tracked down the reason for the test failiures. The function mdd_create() has it clf_flags ALWAYS set to zero so CLFE_NID_BE is never set. Maybe spec->sp_cr_flags might have the proper flags. If not does anyone know a way to extract the open flags we find for mdd_objects? |
| Comment by Gerrit Updater [ 28/Sep/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/52361/ |