[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <66210EA3-EC68-49DA-865F-5068BDA24E8C@redhat.com>
Date: Thu, 05 Jan 2017 11:21:00 -0500
From: "Benjamin Coddington" <bcodding@...hat.com>
To: "Alexander Viro" <viro@...iv.linux.org.uk>
Cc: "Anna Schumaker" <anna.schumaker@...app.com>,
"Trond Myklebust" <trondmy@...marydata.com>,
"Linux NFS Mailing List" <linux-nfs@...r.kernel.org>,
"Linux FS-devel Mailing List" <linux-fsdevel@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] NFS: switch back to ->iterate()
On 15 Dec 2016, at 17:40, Trond Myklebust wrote:
>> On Dec 9, 2016, at 08:41, Benjamin Coddington <bcodding@...hat.com>
>> wrote:
>> @@ -519,13 +508,7 @@ void nfs_prime_dcache(struct dentry *parent,
>> struct nfs_entry *entry)
>> filename.hash = full_name_hash(parent, filename.name, filename.len);
>>
>> dentry = d_lookup(parent, &filename);
>> -again:
>> - if (!dentry) {
>> - dentry = d_alloc_parallel(parent, &filename, &wq);
>> - if (IS_ERR(dentry))
>> - return;
>> - }
>> - if (!d_in_lookup(dentry)) {
>> + if (dentry != NULL) {
>
> This all looks like it is reverting to using an obsolete VFS API.
> I’d
> prefer an ACK from Al as to whether or not this is allowed. Please
> note
> that the rest of the lookup code is still parallelised.
I should've made sure the revert wasn't going to jump back to older VFS
usage. I'll go back over this to make sure that's not the case.
Al, are you hoping to get rid of ->iterate completely? If so, better to
work on this another way.
Ben
Powered by blists - more mailing lists