From: Jeff Layton <jlayton@kernel.org>
To: Mike Snitzer <snitzer@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>, NeilBrown <neil@brown.name>
Cc: linux-nfs@vger.kernel.org
Subject: Re: unable to run NFSD in container if "options sunrpc pool_mode=pernode"
Date: Fri, 23 May 2025 14:40:17 -0400 [thread overview]
Message-ID: <f93f70ce429f2dd6d11f6900808fc4ab737f765f.camel@kernel.org> (raw)
In-Reply-To: <aDC-ftnzhJAlwqwh@kernel.org>
On Fri, 2025-05-23 at 14:29 -0400, Mike Snitzer wrote:
> I don't know if $SUBJECT ever worked... but with latest 6.15 or
> nfsd-testing if I just use pool_mode=global then all is fine.
>
> If pool_mode=pernode then mounting the container's NFSv3 export fails.
>
> I haven't started to dig into code yet but pool_mode=pernode works
> perfectly fine if NFSD isn't running in a container.
>
> Mike
>
> ps. yet another reason why pool_mode=pernode should be the default if
> more than 1 NUMA node ;)
Huh, strange. I've no idea why that would be. What kernel is this?
FWIW, I just built a localio-enabled on a v6.12-uek kernel for our own
purposes yesterday and it's running pool_mode=pernode. It seemed to
work fine as a v3 DS, but I didn't test mounting the container's export
directly.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-05-23 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 18:29 unable to run NFSD in container if "options sunrpc pool_mode=pernode" Mike Snitzer
2025-05-23 18:40 ` Jeff Layton [this message]
2025-05-23 22:19 ` Mike Snitzer
2025-05-23 22:38 ` Mike Snitzer
2025-05-23 22:40 ` Jeff Layton
2025-05-23 23:09 ` Mike Snitzer
2025-05-24 3:53 ` Mike Snitzer
2025-05-24 10:26 ` Jeff Layton
2025-05-24 12:05 ` Jeff Layton
2025-05-24 14:33 ` Mike Snitzer
2025-05-24 15:10 ` Jeff Layton
2025-05-27 13:50 ` Jeff Layton
2025-05-27 21:59 ` Jeff Layton
2025-06-13 12:32 ` Jeff Layton
2025-05-23 18:40 ` Chuck Lever
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=f93f70ce429f2dd6d11f6900808fc4ab737f765f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=snitzer@kernel.org \
/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