On 08/13/2014 04:44 PM, Miklos Szeredi wrote:
On Fri, Jun 6, 2014 at 3:27 PM, Maxim Patlasov wrote:
Hi,
There is a long-standing demand for synchronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.php?msg_
On Fri, Jun 6, 2014 at 3:27 PM, Maxim Patlasov wrote:
> Hi,
>
> There is a long-standing demand for synchronous behaviour of fuse_release:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=19343889
> http://sourceforge.net/mailarchive/message.php?msg_id=29814693
>
> A year ago Avati and me
On 06/09/2014 03:11 PM, John Muir wrote:
On 2014.06.09, at 12:46 , Maxim Patlasov wrote:
On 06/09/2014 01:26 PM, John Muir wrote:
On 2014.06.09, at 9:50 , Maxim Patlasov wrote:
On 06/06/2014 05:51 PM, John Muir wrote:
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
The patch-set resolv
On 2014.06.09, at 12:46 , Maxim Patlasov wrote:
> On 06/09/2014 01:26 PM, John Muir wrote:
>> On 2014.06.09, at 9:50 , Maxim Patlasov wrote:
>>
>>> On 06/06/2014 05:51 PM, John Muir wrote:
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
> The patch-set resolves the problem by ma
On 06/09/2014 01:26 PM, John Muir wrote:
On 2014.06.09, at 9:50 , Maxim Patlasov wrote:
On 06/06/2014 05:51 PM, John Muir wrote:
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
The patch-set resolves the problem by making fuse_release synchronous:
wait for ACK from userspace for FUSE_RELEA
On 2014.06.09, at 9:50 , Maxim Patlasov wrote:
> On 06/06/2014 05:51 PM, John Muir wrote:
>> On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
>>
>>> The patch-set resolves the problem by making fuse_release synchronous:
>>> wait for ACK from userspace for FUSE_RELEASE if the feature is ON.
>> Wh
On 06/06/2014 05:51 PM, John Muir wrote:
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
The patch-set resolves the problem by making fuse_release synchronous:
wait for ACK from userspace for FUSE_RELEASE if the feature is ON.
Why not make this feature per-file with a new flag bit in struct f
On 2014.06.06, at 15:27 , Maxim Patlasov wrote:
> The patch-set resolves the problem by making fuse_release synchronous:
> wait for ACK from userspace for FUSE_RELEASE if the feature is ON.
Why not make this feature per-file with a new flag bit in struct fuse_file_info
rather than as a file-sys
Hi,
There is a long-standing demand for synchronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.php?msg_id=29814693
A year ago Avati and me explained why such a feature would be useful:
http://sourceforge.n
On 4/17/13 1:53 PM, Miklos Szeredi wrote:
On Mon, Apr 15, 2013 at 5:30 PM, Miklos Szeredi wrote:
Let's approach it from the other direction: what if you give back the
write lease on the first flush? It will probably work fine for 99% of
cases, since no other writes are going to happen after t
On Mon, Apr 15, 2013 at 5:30 PM, Miklos Szeredi wrote:
> Let's approach it from the other direction: what if you give back the
> write lease on the first flush? It will probably work fine for 99% of
> cases, since no other writes are going to happen after the first
> flush. For the remaining ca
Hi Miklos,
On 4/15/13 7:08 PM, Miklos Szeredi wrote:
On Thu, Dec 20, 2012 at 1:30 PM, Maxim Patlasov wrote:
Hi,
There is a long-standing demand for syncronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.
On Mon, Apr 15, 2013 at 8:17 PM, Al Viro wrote:
> On Mon, Apr 15, 2013 at 05:30:41PM +0200, Miklos Szeredi wrote:
>> On Mon, Apr 15, 2013 at 5:08 PM, Miklos Szeredi wrote:
>> > For example doing a readlink() on a magic symlink under /proc
>> > shouldn't result in a synchronous call to a fuse file
On Mon, Apr 15, 2013 at 05:30:41PM +0200, Miklos Szeredi wrote:
> On Mon, Apr 15, 2013 at 5:08 PM, Miklos Szeredi wrote:
> > For example doing a readlink() on a magic symlink under /proc
> > shouldn't result in a synchronous call to a fuse filesystem. Making
> > fput() synchronous may actually en
On Mon, Apr 15, 2013 at 5:08 PM, Miklos Szeredi wrote:
> For example doing a readlink() on a magic symlink under /proc
> shouldn't result in a synchronous call to a fuse filesystem. Making
> fput() synchronous may actually end up doing that (even if it's not
> very likely).
Thinking about this a
On Thu, Dec 20, 2012 at 1:30 PM, Maxim Patlasov wrote:
> Hi,
>
> There is a long-standing demand for syncronous behaviour of fuse_release:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=19343889
> http://sourceforge.net/mailarchive/message.php?msg_id=29814693
>
> A few months ago Avati
Hi Miklos,
Any feedback would be highly appreciated.
Thanks,
Maxim
12/20/2012 04:30 PM, Maxim Patlasov пишет:
Hi,
There is a long-standing demand for syncronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/messag
Hi,
There is a long-standing demand for syncronous behaviour of fuse_release:
http://sourceforge.net/mailarchive/message.php?msg_id=19343889
http://sourceforge.net/mailarchive/message.php?msg_id=29814693
A few months ago Avati and me explained why such a feature would be useful:
http://sourcefo
18 matches
Mail list logo
