mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Dan Shelton <dan.f.shelton@gmail.com>, barebox@lists.infradead.org
Subject: Re: NFSv4 boot support?
Date: Tue, 20 Feb 2024 16:28:37 +0100	[thread overview]
Message-ID: <dvhyqjpxezme62dmewvqfeb4kb2szhaz7oysp7qgtd2u7xh3lk@hpascevzd7hv> (raw)
In-Reply-To: <c7901b53-d0a7-4686-9498-3673201d0f62@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]

On Tue, Feb 20, 2024 at 03:17:02PM +0100, Ahmad Fatoum wrote:
> Hello Dan,
> 
> On 19.02.24 03:17, Dan Shelton wrote:
> > On Sat, 17 Feb 2024 at 09:51, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> >>
> >> Hello Antony,
> >>
> >> On 05.02.24 10:59, Antony Pavlov wrote:
> >>> On Wed, 31 Jan 2024 22:37:50 +0100
> >>> Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> >>>
> >>> Hi All!
> >>>
> >>>> Hello Dan,
> >>>>
> >>>> On 31.01.24 22:03, Dan Shelton wrote:
> >>>>> Hello!
> >>>>>
> >>>>> Does barebox support booting from a NFSv4 filesystem, e.g. boot from
> >>>>> NFSv4 filesystem into a Linux NFSv4 netroot (diskless machine)?
> >>>>
> >>>> The barebox network stack only does UDP/IP. There have been attempts to
> >>>> bring a TCP stack into barebox, but none have so far succeeded to
> >>>> make it mainline. This is a hard requirement before we can consider
> >>>> supporting NFSv4. I hope that lwIP could fill this gap in the future,
> >>>> but no one is actively continuing this work as far as I am aware[1].
> >>>
> >>> I have started integration on picotcp into barebox in 2015, see
> >>>   https://lore.barebox.org/barebox/1436991230-14251-10-git-send-email-antonynpavlov@gmail.com/T/
> >>>
> >>> At the moment I have WIP barebox-v2023.11 with integrated picotcp 2.1:
> >>>
> >>>   https://github.com/frantony/barebox/tree/20231127.picotcp
> >>
> >> Cool. Looking at Oleksij's repo, it was based on your work. How well does
> >> picotcp work for you? What open issues remain with the patch stack? Is the
> >> barebox integration actively used in projects?
> >>
> >> Is https://github.com/tass-belgium/picotcp the official repository? This hasn't
> >> seen development activity in 5 years. lwIP on the other hand still sees active
> >> development.
> >>
> >> Regarding the license, inclusion of BSD-licensed code is ok. You can check out
> >> the LICENSES/ subdirectory for the licenses covering barebox.
> > 
> > If TCP support lands in barebox, how fast can NFSv4 support be implemented?
> 
> Depends on who's volunteering to do it. :-)
> If your question instead is how much effort a NFSv4 port would be, Uwe did the
> NFSv3 port and may have an guesstimate for this?

Without having taken a deeper look: I think the step from NFSv2 to NFSv3
was much easier than NFSv3 -> NFSv4 will be. For NFSv3 support I needed
4 full work days.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-02-20 15:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 21:03 Dan Shelton
2024-01-31 21:37 ` Ahmad Fatoum
2024-02-05  9:59   ` Antony Pavlov
2024-02-17  8:51     ` Ahmad Fatoum
2024-02-19  2:17       ` Dan Shelton
2024-02-20 14:17         ` Ahmad Fatoum
2024-02-20 15:28           ` Uwe Kleine-König [this message]
2024-02-19 21:43       ` Antony Pavlov
2024-02-20 13:53       ` Alessandro Rubini
2024-02-26 12:17         ` Ahmad Fatoum
2024-03-08 10:23         ` Sascha Hauer
2024-03-09 10:01         ` Alessandro Rubini
2024-02-28  7:26       ` Antony Pavlov
2024-02-28  9:20         ` Sascha Hauer
2024-02-28 11:50           ` Antony Pavlov
2024-02-28 12:27             ` Sascha Hauer
2024-02-05 18:41   ` Antony Pavlov
2024-02-06  4:40     ` Dan Shelton

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=dvhyqjpxezme62dmewvqfeb4kb2szhaz7oysp7qgtd2u7xh3lk@hpascevzd7hv \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=dan.f.shelton@gmail.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