linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <schumaker.anna@gmail.com>
To: Steve Dickson <SteveD@redhat.com>,
	Benjamin Coddington <bcodding@uvm.edu>
Cc: linux-nfs@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] nfsidmap: use multiple child keyrings
Date: Mon, 24 Mar 2014 18:10:29 -0400	[thread overview]
Message-ID: <5330AD55.50004@gmail.com> (raw)
In-Reply-To: <5330A217.6020607@RedHat.com>

On 03/24/2014 05:22 PM, Steve Dickson wrote:
>
> On 03/24/2014 05:03 PM, Benjamin Coddington wrote:
>> On Mar 24, 2014, at 3:51 PM, Steve Dickson <SteveD@redhat.com> wrote:
>>
>>>>> Finally, what -n value do plan on using? Maybe a blurb in the man page
>>>>> on what a good number is and why....
>>>> I've got this running now with -n160, since 
>>>> we have ~60K distinct uid/gid s.  Ideally, I'd like to re-submit 
>>>> this to self-scale which wouldn't require any sysadmin tuning, 
>>>> but I haven't had the time.  Really, this is just a quick fix 
>>>> for the brokenness that's in current RHEL and less-new Fedora.
>>> The brokenness in RHEL will be healing very soon... See 
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1033708. RHEL is 
>>> basically going back to using rpc.idmapd on the client and
>>> nfsidmap is going away... It as just a bad dream... It never
>>> happen! ;-)
>> This BZ says the fix is coming in nfs-utils by removing the nfsidmap command.  
> Yeah.. I bet the RHEL police are not going to be happy about that... so I
> might have to put it back... 
>
>> But IIRC, unless the kernel side of the idmapper is changed, it will exec request-key 
>> for every lookup before falling back to the upcall, and there's no cache in front of that.  
>> Isn't that going to have some performance problems?  
> I don't thinks so, since things will eventually get cached but I'll definitely look into it... 

The fallback upcall version uses the "id_legacy" keyring to cache results.  A bigger keyring might be the best solution.

Anna
>
>> I'm much more interested in getting the keyrings to work, since they seem to 
>> offer significant performance gains.
> I too, but the back port of the current key is a bit too much for RHEL at this point.
>> If RH is going to change the kernel side of the idmapper to only upcall, then I'd be satisfied to use that.
> It was a bone-head decision on my part to flip this type of switch midstream... 
> I too just want to put things back to the way were,,,
>
> steved.
>
>> Ben
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2014-03-24 22:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 21:08 [PATCH] nfsidmap: use multiple child keyrings Benjamin Coddington
2014-03-24 17:00 ` Steve Dickson
2014-03-24 18:00   ` Benjamin Coddington
2014-03-24 19:51     ` Steve Dickson
2014-03-24 21:03       ` Benjamin Coddington
2014-03-24 21:22         ` Steve Dickson
2014-03-24 22:10           ` Anna Schumaker [this message]
2014-03-24 23:57       ` Steve Dickson
2014-03-25  0:15         ` Benjamin Coddington
2014-03-25  9:35         ` David Howells
2014-03-25 12:49           ` Benjamin Coddington
2014-03-25  9:29       ` David Howells
2014-03-25 10:41         ` Steve Dickson
2014-03-25  9:34     ` David Howells
2014-03-25 12:56       ` Benjamin Coddington
2014-03-25 13:30       ` David Howells

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=5330AD55.50004@gmail.com \
    --to=schumaker.anna@gmail.com \
    --cc=SteveD@redhat.com \
    --cc=bcodding@uvm.edu \
    --cc=dhowells@redhat.com \
    --cc=linux-nfs@vger.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;
as well as URLs for NNTP newsgroup(s).