public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Mike Snitzer <snitzer@kernel.org>
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>,
	NeilBrown <neil@brown.name>
Subject: Re: unable to run NFSD in container if "options sunrpc pool_mode=pernode"
Date: Fri, 23 May 2025 14:40:25 -0400	[thread overview]
Message-ID: <f027319a-378d-4b91-a418-c45218fb7a21@oracle.com> (raw)
In-Reply-To: <aDC-ftnzhJAlwqwh@kernel.org>

On 5/23/25 2:29 PM, Mike Snitzer wrote:
> ps. yet another reason why pool_mode=pernode should be the default if
> more than 1 NUMA node ;)

Easier said than done. During bake-a-thon, I mentioned there are some
historical discussions about this. Two I found:

https://lore.kernel.org/linux-nfs/313d317dc0ca136de106979add5695ef5e2101e7.camel@hammerspace.com/

And the review comments on this patch:

https://lore.kernel.org/linux-nfs/20240715074657.18174-14-neilb@suse.de/


-- 
Chuck Lever

      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
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 [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=f027319a-378d-4b91-a418-c45218fb7a21@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --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