linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Benny Halevy <bhalevy@primarydata.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	bfields@redhat.com, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: state lock elimination
Date: Wed, 16 Oct 2013 11:22:38 -0700	[thread overview]
Message-ID: <20131016182238.GA2944@infradead.org> (raw)
In-Reply-To: <525E4C88.9050701@primarydata.com>

On Wed, Oct 16, 2013 at 11:21:28AM +0300, Benny Halevy wrote:
> I tried reducing the lock scope but the problem is that we hash state
> on objects with different scopes of access, particularly net/client vs. file
> and the hashing needs to be consistent and atomic.

Lists, Hashes or similar lookup data structures are generally not the
hard part, as it's enough to lock the data structure that the hash or
list hangs off.  No need to involve looks in the structure pointed to.


  reply	other threads:[~2013-10-16 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131015211445.GA23636@infradead.org>
     [not found] ` <525DB943.3010707@primarydata.com>
     [not found]   ` <20131016064243.GA28758@infradead.org>
2013-10-16  8:21     ` state lock elimination Benny Halevy
2013-10-16 18:22       ` Christoph Hellwig [this message]
     [not found] ` <525E2C5C.4020104@primarydata.com>
     [not found]   ` <20131016064649.GB28758@infradead.org>
2013-10-16  8:45     ` nfs4_file usage Benny Halevy
2013-10-16  8:51       ` Christoph Hellwig
2013-10-16 12:18         ` Benny Halevy
2013-10-16 12:33           ` Christoph Hellwig
2013-10-16 12:48             ` Benny Halevy

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=20131016182238.GA2944@infradead.org \
    --to=hch@infradead.org \
    --cc=bfields@redhat.com \
    --cc=bhalevy@primarydata.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).