From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Joaquin Varela" <joaquinvarela@neatech.ar>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [RFC] Native ZFS over NVMe/TCP storage backend for Proxmox VE
Date: Thu, 24 Sep 2026 11:26:41 +0200 [thread overview]
Message-ID: <DLNFTPM4FLZK.2G79A724QKH54@proxmox.com> (raw)
In-Reply-To: <CANSq6_+oNfTqEQozswjaqLgX7LyvcbOnd0P9ccgREWT_comWAg@mail.gmail.com>
Hi Joaquin!
Sorry for taking so long -- I'm finally getting around to reviewing your
patch series. Expect a review on the mailing list either this week (if
I'm really quick) or next week.
Sorry again, and thanks for being so patient! Had a lot of things in my
backlog to sort out.
Have a good one,
Max
On Thu Sep 24, 2026 at 5:53 AM CEST, Joaquin Varela wrote:
> Hi Max,
>
> I wanted to follow up on the zfsnvme v2 series sent on August 2. We are
> interested in deploying this type of shared ZFS over NVMe/TCP storage in
> production, so feedback on the design and any blockers you see for upstream
> integration would be especially valuable before we make that decision.
>
> Have you had a chance to look at the series, or is it still waiting in the
> review queue? If a full review will take longer, even a brief indication of
> architectural concerns or the likely next step would help us plan.
>
> I know review time is limited, and I appreciate your help.
>
> Kind regards,
> Joaquin Varela
>
> On Wed, Sep 9, 2026 at 11:45 AM Joaquin Varela <joaquinvarela@neatech.ar>
> wrote:
>
> > Hi Max,
> >
> > Just a gentle follow-up on the zfsnvme v2 patch series I sent on
> > August 2. I understand you have a review backlog, and I appreciate
> > your time.
> >
> > Please let me know if there is any additional information about the
> > design or test setup that would help with the review, or if you would
> > prefer any changes to the way the series is organized.
> >
> > For convenience, here are the three series:
> >
> > pve-storage:
> >
> > https://lore.proxmox.com/pve-devel/cover.1785636979.git.joaquinvarela@neatech.ar/T/
> >
> > pve-manager:
> >
> > https://lore.proxmox.com/pve-devel/cover.1785636980.git.joaquinvarela@neatech.ar/T/
> >
> > pve-docs:
> >
> > https://lore.proxmox.com/pve-devel/cover.1785636981.git.joaquinvarela@neatech.ar/T/
> >
> > Thank you again for your time and interest.
> >
> > Kind regards,
> > Joaquin Varela
> >
prev parent reply other threads:[~2026-09-24 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 16:23 [RFC] Native ZFS over NVMe/TCP storage backend for Proxmox VE Joaquin Varela
2026-07-21 11:45 ` Max R. Carrara
2026-08-02 3:20 ` Joaquin Varela
2026-08-07 9:46 ` Max R. Carrara
2026-09-09 14:45 ` Joaquin Varela
2026-09-24 3:53 ` Joaquin Varela
2026-09-24 9:26 ` Max R. Carrara [this message]
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=DLNFTPM4FLZK.2G79A724QKH54@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=joaquinvarela@neatech.ar \
--cc=pve-devel@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.