From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69393C4338F for ; Mon, 2 Aug 2021 03:13:11 +0000 (UTC) Received: from pdx1-mailman02.dreamhost.com (pdx1-mailman02.dreamhost.com [64.90.62.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id DDCCD61050 for ; Mon, 2 Aug 2021 03:13:09 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org DDCCD61050 Authentication-Results: mail.kernel.org; dmarc=pass (p=none dis=none) header.from=lists.lustre.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.lustre.org Received: from pdx1-mailman02.dreamhost.com (localhost [IPv6:::1]) by pdx1-mailman02.dreamhost.com (Postfix) with ESMTP id 3A6BD350B41; Sun, 1 Aug 2021 20:13:09 -0700 (PDT) Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) by pdx1-mailman02.dreamhost.com (Postfix) with ESMTP id A74D0350B5C for ; Sun, 1 Aug 2021 20:13:06 -0700 (PDT) Received: by mail-yb1-f170.google.com with SMTP id d73so1444230ybc.10 for ; Sun, 01 Aug 2021 20:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jAuehAzDbFYXWAT0sJkI8ETZb9xyKQ4HW7uW8e7K2dI=; b=TuDrWpDia6QoLzYOmi6Lj4Z5f1N6+SlAL6l6Ud28dLceFj6LPW8Nad/E2xRX7nRlip Z63hezyH9dd9VhZEFYroV/5Q45tJGWwH2zArf+RC3MsjgqWMA23DdSJK0ara2nDdgA2q pFgY89UUnW0oW4l6iu5Vky2a2x9GoZttoLn+zBjf4t2TbeyGPSySD+7aRUTPueRb/h2V k3vLgqBllPAA2ez3BsfqlvNykjwram43TcAItCJ5C7SdBjpEeTS3SOMozuBjmzPQyG8d 4a7DqVnG5ro5Phs740GD8aT6aSBQCVZd2z4WpmtC1fcbMe1A1LT5AK/HTXDANg60YKmq dJsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jAuehAzDbFYXWAT0sJkI8ETZb9xyKQ4HW7uW8e7K2dI=; b=csvFx0UsyyjzUd9hc+F65upEVI5Cse1px+52vWDwjV6TVJGZw41eT3P/0RFInuHqmw 5uoDedi2nPEeUuVsoQzuRzv1YG7ra/58vZzrDpZa0jrMuoV2yH1bVc9jmsibL/rbzlLJ hP1Ysqo0YY4FsDdZAre13IlrXPu5ySzE/ZBF6zkRLg02BhZdv4bH+L3Cm6yK4BhWHx/H m8F9HxaF4f5UmzZXKg+0f9+QdwXH1a5TN//buDJeOc2s39+6Vy9BDmJRmU2NaoKkN/oe IzAsPXyjt++Ro5LQQ/tjauBWN2Sanu6ckEcYa4qamNjcEG94Z1QtOx0fzzTZ/waPdsB2 JwTg== X-Gm-Message-State: AOAM532TAJqEfg4JmXomR2MTLme6U8NgEVrzgGxnwnm5KNsyOT+NP4iT VyspiFD+2KOFz05kooj6YI58LLPD63hB7LqCfs3W2A== X-Google-Smtp-Source: ABdhPJxkcQtf+VeZi14MpwHMlpqmi3Z/94eAdXmw0tDUHGPo3scDyhhaBC3Ghp0EPOQt5n8jcKvOla/tQGb8G0ubdTI= X-Received: by 2002:a25:6e45:: with SMTP id j66mr18203769ybc.449.1627873985870; Sun, 01 Aug 2021 20:13:05 -0700 (PDT) MIME-Version: 1.0 References: <846A7FB8-D265-4CCD-B61C-1D18A6FCA8FF@ddn.com> <5C1FCECB-995B-47BA-9D98-DA00CAF42B3F@ddn.com> In-Reply-To: Date: Mon, 2 Aug 2021 11:12:29 +0800 Message-ID: To: Peter Jones Subject: Re: [lustre-devel] Lustre Arm64 Development and Release X-BeenThere: lustre-devel@lists.lustre.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "For discussing Lustre software development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Xinliang Liu via lustre-devel Reply-To: Xinliang Liu Cc: "lustre-devel@lists.lustre.org" Content-Type: multipart/mixed; boundary="===============7842685498681783715==" Errors-To: lustre-devel-bounces@lists.lustre.org Sender: "lustre-devel" --===============7842685498681783715== Content-Type: multipart/alternative; boundary="000000000000aad72505c88af221" --000000000000aad72505c88af221 Content-Type: text/plain; charset="UTF-8" On Fri, 30 Jul 2021 at 20:46, Peter Jones wrote: > Xinliang > > > > There are presently no specific plans/timeline around providing an aarch64 > release. This would certainly be something that we could look into if there > remains consistent interest/engagement on this. Most of the issues on that > short list of tickets have been around for some years already. I suggest > that we revisit this topic when the list is down to 1-2 remaining issues. > Hi Peter, got it. We will continue fixing the arm bug list. Hope we will make good progress soon. Xinliang > > > Peter > > > > *From: *Xinliang Liu > *Date: *Thursday, July 29, 2021 at 8:49 PM > *To: *Peter Jones > *Cc: *Kevin Zhao , "lustre-devel@lists.lustre.org" > > *Subject: *Re: [lustre-devel] Lustre Arm64 Development and Release > > > > Hi Peter and Lustre team, > > > > On Tue, 29 Jun 2021 at 20:47, Peter Jones wrote: > > Kevin > > > > This would be a good starting point - > https://jira.whamcloud.com/issues/?filter=15555 > > > > Recently, we've set up all-in-one and multi-node CentOS8 aarch64 Lustre > test environments which include both server and client. > And we've done some basic file read/write manual tests and verified the > first bug #LU-10073 of the filter bug list, it's very exciting that no > issues were found on aarch64 CentOS8. > > We will continue to verify other bugs on the filter list. But we currently > are very interested in the goal of arm64 release. So that users can > directly download aarch64 release from Lustre web site without building by > themself. And we eager to know more details about the aarch64 release: > > 1) Any schedule timeline or plan for aarch64 release? > 2) If there is no now, how to make it happen? > 3) What are things we need to offer aarch64 releases? Or what resources > are missing? > We are looking forward to your reply. And will continue to contribute more > to the Lustre community. Thanks. > > > > Xinliang > > > > > > Peter > > > > *From: *Kevin Zhao > *Date: *Tuesday, June 29, 2021 at 5:44 AM > *To: *Peter Jones > *Cc: *"lustre-devel@lists.lustre.org" , > Xinliang Liu > *Subject: *Re: [lustre-devel] Lustre Arm64 Development and Release > > > > Hi Peter, > > > > That's great! We can help to follow and fix test failures. Could you point > us some test failure links or logs? So that we can kick off our work and > reproduce the failure in our local lab. > > Thanks! > > > > On Tue, 29 Jun 2021 at 20:41, Peter Jones wrote: > > Hi Kevin > > > > Various people have asked this question over the last couple of years. We > have machines that could be used for CI (Arm clients are being routinely > tested) but the challenge has been to have someone follow through and work > through test failures and take responsibility for vetting the tests in an > ongoing basis. > > > > Peter > > > > *From: *lustre-devel on behalf of > Kevin Zhao via lustre-devel > *Reply-To: *Kevin Zhao > *Date: *Tuesday, June 29, 2021 at 5:29 AM > *To: *"lustre-devel@lists.lustre.org" > *Cc: *Xinliang Liu > *Subject: *[lustre-devel] Lustre Arm64 Development and Release > > > > Hi Lustre, > > > > Greetings! > > I'm Kevin Zhao, and cc'ed Xinliang Liu, we are from Linaro. We are working > on Arm64 storage enablement and Lustre is definitely on top of our list. > We've received some requests from our members about Lustre support on > Arm64. > > > > So I'm writing to ask the current status of Lustre on Arm64. I noticed > that there are some pages recording Lustre build method on Arm64 as Link > and > some Jira cards . But I don't > see official or experimental release on Arm64. So my question is: > > 1. if there some gap or effort needs to be done in order to offer arm64 > release? We are very interested and can help to work on that. > > 2. If there CI resources needs in order to achieve this? At Linaro we also > have some machine resources to serve as the CI machines. > > > > Thanks a lot for your reply in advance and look forward to work with you > in the community! > > > > -- > > *Best Regards* > > *Kevin Zhao* > > Tech Lead, LDCG Cloud Infrastructure > > Linaro Vertical Technologies > > IRC(freenode): kevinz > > Slack(kubernetes.slack.com): kevinz > > kevin.zhao@linaro.org | Mobile/Direct/Wechat: > +86 18818270915 > > > > > > > -- > > *Best Regards* > > *Kevin Zhao* > > Tech Lead, LDCG Cloud Infrastructure > > Linaro Vertical Technologies > > IRC(freenode): kevinz > > Slack(kubernetes.slack.com): kevinz > > kevin.zhao@linaro.org | Mobile/Direct/Wechat: > +86 18818270915 > > > > --000000000000aad72505c88af221 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, 30 Jul 2021 at 20:46, Peter Jones= <pjones@whamcloud.com> w= rote:

Xinlia= ng

=C2=A0

There = are presently no specific plans/timeline around providing an aarch64 releas= e. This would certainly be something that we could look into if there remai= ns consistent interest/engagement on this. Most of the issues on that short list of tickets have been around fo= r some years =C2=A0already. I suggest that we revisit this topic when the l= ist is down to 1-2 remaining issues.


Hi Peter, got it. We will continue fixing the arm bug list= . Hope we will make good progress soon.

Xinliang

=C2=A0

=C2=A0

Peter<= u>

=C2=A0

From: = Xinliang Liu <xinliang.liu@linar= o.org>
Date: Thursday, July 29, 2021 at 8:49 PM
To: Peter Jones <pjones@whamcloud.com>
Cc: Kevin Zhao <kevin.zhao@linaro.org>, "lustre-devel@lists.lustre.org&= quot; <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] Lustre Arm64 Development and Release<= /u>

=C2=A0

Hi Peter and Lustre team,

=C2=A0

On Tue, 29 Jun 2021 at 20:47, Peter Jones <pjones@whamcloud.com> wrote:

=C2=A0

Recently, we've set up all-in-one and multi-node= CentOS8 aarch64 Lustre test environments which include both server and cli= ent.
And we've done some basic file read/write manual tests and verified the= first bug #LU-10073 of the filter bug list, it's very exciting that no= issues were found on aarch64 CentOS8.
=C2=A0
We will continue to verify other bugs on the filter list. But we currently = are very interested in the goal of arm64 release. So that users can directl= y download aarch64 release from Lustre web site without building by themsel= f. And we eager to know more details about the aarch64 release:

1) Any schedule timeline or plan for aarch64 release= ?
2) If there is no now, how to make it happen?
3) What are things we need to offer aarch64 releases? Or what resources are= missing?
We are looking forward to your reply. And will continue to contribute more = to the Lustre community. Thanks.

=C2=A0

Xinliang

=C2=A0

=C2=A0=

Peter<= /span>

=C2=A0=

=C2=A0

Hi Peter,

=C2=A0

That's great! We can help to follow and fix test= failures. Could you point us some test failure links or logs? So that we c= an kick off our work and reproduce the failure in our local lab.

Thanks!

=C2=A0

On Tue, 29 Jun 2021 at 20:41, Peter Jones <pjones@whamcloud.com> wrote:

Hi Kev= in

=C2=A0=

Variou= s people have asked this question over the last couple of years. We have ma= chines that could be used for CI (Arm clients are being routinely tested) but the challenge has been to have someone follow throug= h and work through test failures and take responsibility for vetting the te= sts in an ongoing basis.

=C2=A0=

Peter<= /span>

=C2=A0=

From: lustre-devel <lust= re-devel-bounces@lists.lustre.org> on behalf of Kevin Zhao via lustr= e-devel <lustre-devel@lists.lustre.org>
Reply-To: Kevin Zhao <kevin.zhao@linaro.org>
Date: Tuesday, June 29, 2021 at 5:29 AM
To: "lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org<= /a>>
Cc: Xinliang Liu <
xinliang.liu@linaro.org>
Subject: [lustre-devel] Lustre Arm64 Development and Release<= u>

=C2=A0

Hi Lustre,

=C2=A0

Greetings!

I'm Kevin Zhao, and cc'ed Xinliang Liu, we a= re from Linaro. We are working on Arm64 storage enablement and Lustre is de= finitely on top of our list. We've received some requests from our members about Lustre support on Arm64.=C2=A0

=C2=A0

So I'm writing to ask the current status of Lust= re on Arm64. I noticed that there are some pages recording Lustre build met= hod on Arm64 as Link and some Jira cards. But I don't see official or experimental=C2=A0release o= n Arm64. So my question is:

1. if there some gap or effort needs to be done in o= rder to offer arm64 release? We are very interested and can help to work on= that.

2. If there CI resources needs in order to achieve t= his? At Linaro we also have some machine resources to serve as the CI machi= nes.

=C2=A0

Thanks a lot for your reply in=C2=A0advance and look= forward to work with you in the community!

=C2=A0

--

Best Regards

Kevin Zhao

Tech Lead, LDCG Cloud Infrastructure

Linaro Vertical Technologies

IRC(freenode): kevinz

Slack(kubernete= s.slack.com): kevinz

kevin= .zhao@linaro.org=C2=A0| Mobile/Direct/Wechat:=C2=A0 +86 18818270915=C2= =A0

=C2=A0


=C2=A0

--

Best Regards

Kevin Zhao

Tech Lead, LDCG Cloud Infrastructure

Linaro Vertical Technologies

IRC(freenode): kevinz

Slack(kubernete= s.slack.com): kevinz

kevin= .zhao@linaro.org=C2=A0| Mobile/Direct/Wechat:=C2=A0 +86 18818270915=C2= =A0

=C2=A0

--000000000000aad72505c88af221-- --===============7842685498681783715== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lustre-devel mailing list lustre-devel@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org --===============7842685498681783715==--