From: "Yitschak, Yehuda via lustre-devel" <lustre-devel@lists.lustre.org>
To: "Simmons, James" <simmonsja@ornl.gov>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] lnet selftest using large NIDs (16 byte)
Date: Thu, 3 Nov 2022 20:07:06 +0000 [thread overview]
Message-ID: <f24018236ca04439b556c6beb7a25d5d@amazon.com> (raw)
> There is no support for this work in 2.12. You are going to have to move to a
> newer lustre version. LND forward
> porting shouldn't be to painful. The biggest change is the LNet health work
> but it's not a hard requirement.
> What will need to be changed is support for the large nid support. By that I
> mean moving from
>
> lnet_nid_t -> struct lnet_nid
>
> The port will be easier than you think.
>
Thanks for clarifying. By hacking the addressing I mean I use 4 bytes NID and just patch the address in the LND.
Last time I moved Lustre versions my main issues was with the build and install process, not the actual rebase
I found it challenging to build lustre for my specific kernel and Distro.
Anyway, I'll give a try and see how it goes.
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next reply other threads:[~2022-11-03 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 20:07 Yitschak, Yehuda via lustre-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-03 15:57 [lustre-devel] lnet selftest using large NIDs (16 byte) Yitschak, Yehuda via lustre-devel
2022-11-03 14:23 Simmons, James via lustre-devel
2022-11-03 7:31 Yitschak, Yehuda via lustre-devel
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=f24018236ca04439b556c6beb7a25d5d@amazon.com \
--to=lustre-devel@lists.lustre.org \
--cc=simmonsja@ornl.gov \
--cc=yehuday@amazon.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).