From: Martin Wege <martin.l.wege@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Dan Shelton <dan.f.shelton@gmail.com>,
Cedric Blancher <cedric.blancher@gmail.com>,
Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: Mount NFSv4.2 filesystem in barebox?
Date: Tue, 4 Mar 2025 22:50:00 +0100 [thread overview]
Message-ID: <CANH4o6PN3tJC+zLt_eLeKzJ6BVFnGo+vYFDF+9Hjp9x6oz626g@mail.gmail.com> (raw)
In-Reply-To: <3ba4d5f3-9679-4a32-a3e7-a8c958107df9@pengutronix.de>
On Mon, Mar 3, 2025 at 9:40 AM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> Hi,
>
> On 28.02.25 11:57, Sascha Hauer wrote:
> > On Fri, Feb 21, 2025 at 12:54:00PM +0100, Martin Wege wrote:
> >> On Wed, Feb 12, 2025 at 3:33 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >>>
> >>> Hi Martin,
> >>>
> >>> On Tue, Feb 11, 2025 at 01:56:58PM +0100, Martin Wege wrote:
> >>>> Hello!
> >>>>
> >>>> Does barebox have support to mount a NFSv.2 filesystem?
> >>>
> >>> No, not yet. For NFSv4 we would first need TCP support. While we started
> >>> to integrate a TCP stack we are not there yet unfortunately.
> >>
> >> How long is this going to take?
> >
> > I don't think this will happen anytime soon. It's quite some work and
> > our bandwidth for adding such a feature without (paying) customer
> > demand is limited.
> >
> > That said, the lack of NFSv4 support is nagging me personally as well.
>
> We had a discussion about this last year, but it didn't result in any
> upstream code yet:
> https://lore.barebox.org/barebox/CAAvCNcCZhS8mkvdgcJ2L-eiur+OxgWEXRLnadO_HFyHfSi7WFA@mail.gmail.com/
>
> One question that I still have, is what do you use NFSv4 for?
> Is it just for development and your IT is disabling NFSv3?
No, NFSv4.1 (NFSv4.0 is obsolete due to bugs) offers better
performance, more flexibility, smaller footprint, better caching
(delegations), ACLs, SELinux support, and can be tunneled through
firewalls because it only uses TCP port 2049 and nothing else.
>
> Do you use it in the field?
Yes, we do
>
> Knowing about the use case helps with prioritizing future work.
> As it stands, NFS is mostly understood as development feature and
> it's expected so far that interested users will be able to provide
> a NFSv3 UDP server in their development network.
No, NFS is not only a development feature. For example CERN uses NFS
boot (with patched NFSv4.1 stack) in radiation environments - that
saves a SSD per embedded machine, which is typically one of the most
affected pieces from radiation. AIRBUS also uses nfsboot in their
equipment and flight deck systems.
So yes, you would have customers for NFSv4.1 support in barebox.
Thanks,
Martin
next prev parent reply other threads:[~2025-03-04 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 12:56 Martin Wege
2025-02-12 14:33 ` Sascha Hauer
2025-02-21 11:54 ` Martin Wege
2025-02-28 10:57 ` Sascha Hauer
2025-03-03 8:40 ` Ahmad Fatoum
2025-03-04 21:50 ` Martin Wege [this message]
2025-03-05 11:30 ` David Jander
2025-03-05 12:51 ` Ahmad Fatoum
2025-03-05 13:55 ` David Jander
2025-03-07 14:40 ` Dan Shelton
2025-03-05 12:03 ` Ahmad Fatoum
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=CANH4o6PN3tJC+zLt_eLeKzJ6BVFnGo+vYFDF+9Hjp9x6oz626g@mail.gmail.com \
--to=martin.l.wege@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=cedric.blancher@gmail.com \
--cc=dan.f.shelton@gmail.com \
--cc=s.hauer@pengutronix.de \
/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