All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Bon <stefbon@gmail.com>
To: "fuse-devel@lists.sourceforge.net"
	<fuse-devel@lists.sourceforge.net>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [fuse-devel] Changes in 4.7.
Date: Tue, 31 May 2016 18:25:24 +0200	[thread overview]
Message-ID: <CANXojcxpUBEooBck=5k6SUQUMj+j1BCeq4dGCTnE4Uv3N8ODMQ@mail.gmail.com> (raw)
In-Reply-To: <87shwy8b38.fsf@thinkpad.rath.org>

Hi,

I've been thinking about the non serialized readdirs. I do not understand.
Readdirs have to be serialized, since the offset of the next readdir
(belonging to the opendir) is known when the current readdir is
finished:
"start where current left".

So it means probably that lookup (which in fact is only a read only
operation) of a name in a directory can be done while a readdir
is active on the same directory.

Or something else? Two readdirs (or more) belonging to different
opendirs active on the same directory?

Stef

  parent reply	other threads:[~2016-05-31 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANXojcwuLVpyqkXxcUhKdG=nDEp-XspR4PtDerpoqO2FmMLp5w@mail.gmail.com>
2016-05-31  7:17 ` [fuse-devel] Changes in 4.7 Miklos Szeredi
2016-05-31 10:57   ` Stef Bon
2016-05-31 11:09     ` Miklos Szeredi
     [not found]   ` <nijg09$6k0$1@ger.gmane.org>
     [not found]     ` <CAJfpegvJoSK6fQEGWj_uEQF8q2jYmdqUyKy1-m5DxFMUFc0rEg@mail.gmail.com>
     [not found]       ` <CAJfpeguV3H_oC=5FM3G8tVsrY7Fiy2LX0JKttFBGQWN+SC6_YQ@mail.gmail.com>
     [not found]         ` <87shwy8b38.fsf@thinkpad.rath.org>
2016-05-31 16:25           ` Stef Bon [this message]
2016-05-31 17:22             ` Stef Bon
2016-05-31 17:44             ` Al Viro
2016-05-31 18:44               ` Stef Bon
2016-05-31 20:29                 ` Al Viro
2016-06-01 12:32                   ` Stef Bon
2016-06-01 13:52                     ` Al Viro
2016-06-01 14:44                       ` Stef Bon

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='CANXojcxpUBEooBck=5k6SUQUMj+j1BCeq4dGCTnE4Uv3N8ODMQ@mail.gmail.com' \
    --to=stefbon@gmail.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.