From: Ian Kent <raven@themaw.net>
To: Nick Piggin <npiggin@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
aelder@sgi.com, Nick Piggin <npiggin@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
David Howells <dhowells@redhat.com>
Subject: Re: [announce] vfs-scale git tree update
Date: Thu, 13 Jan 2011 11:20:28 +0800 [thread overview]
Message-ID: <1294888828.2757.30.camel@perseus> (raw)
In-Reply-To: <AANLkTin9ac1r_Hur4w=cxkCg2Z-JVYRCwsR6KeZ+9b=R@mail.gmail.com>
On Thu, 2011-01-13 at 13:14 +1100, Nick Piggin wrote:
> On Thu, Jan 13, 2011 at 12:48 PM, Ian Kent <raven@themaw.net> wrote:
> > On Thu, 2011-01-13 at 12:01 +1100, Nick Piggin wrote:
> >> Hm, what are the concurrencies that you need protection from?
> >
> > Ha, I think I'm wrong about this, after looking more closely at this I'm
> > struggling to see why autofs4_lock is needed at all.
>
> Well you did send me a series of patches to remove it, but
> unfortunately that was just as you made some larger changes
> to autofs4 upstream and I wasn't able to keep them up to date.
>
> It would be much appreciated if you had time to take another
> look at all the locking and streamline it.
I have started looking at it but just the autofs4_lock.
As you know, we have some significant autofs changes in progress, so I
don't want to spend a huge amount of time testing (and the testing does
take a long time) against source that will be very different. So far I
can't see that the autofs4_lock will introduce any problem so I want to
leave it for now and (probably) eliminate it in the new code since that
will need changes as well and will need to be re-tested.
I'd appreciate it if you could find time to reply to David's questions
about the changes to our d_automount patch series. Although, based on
our previous discussion, I think he has it about right, but a word or
two from you would be really helpful.
Ian
next prev parent reply other threads:[~2011-01-13 3:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 7:58 [announce] vfs-scale git tree update Nick Piggin
2011-01-11 16:34 ` Alex Elder
2011-01-11 16:51 ` Linus Torvalds
2011-01-11 17:57 ` Alex Elder
2011-01-11 18:13 ` Linus Torvalds
2011-01-12 3:55 ` Nick Piggin
2011-01-12 3:59 ` Ian Kent
2011-01-12 4:06 ` Nick Piggin
2011-01-12 4:06 ` Linus Torvalds
2011-01-12 4:41 ` Ian Kent
2011-01-12 5:17 ` Ian Kent
2011-01-13 1:01 ` Nick Piggin
2011-01-13 1:48 ` Ian Kent
2011-01-13 2:14 ` Nick Piggin
2011-01-13 3:20 ` Ian Kent [this message]
2011-01-13 3:22 ` Nick Piggin
2011-01-12 4:15 ` Ian Kent
2011-01-12 20:11 ` Alex Elder
2011-01-13 2:23 ` Ian Kent
2011-01-13 3:03 ` Ian Kent
2011-01-13 17:09 ` Alex Elder
2011-01-12 4:49 ` Aneesh Kumar K. V
2011-01-12 5:01 ` Ian Kent
2011-01-13 0:58 ` Nick Piggin
2011-01-13 1:46 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2011-01-05 10:25 Nick Piggin
2011-01-05 21:00 ` Anca Emanuel
2010-12-22 9:53 Nick Piggin
2010-12-22 10:22 ` Sedat Dilek
2010-12-22 10:38 ` Sedat Dilek
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=1294888828.2757.30.camel@perseus \
--to=raven@themaw.net \
--cc=aelder@sgi.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=npiggin@kernel.dk \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).