fam
[Top] [All Lists]

[fam] Re: [prepatch] Directory Notification

To: Erez Zadok <ezk@xxxxxxxxxxxxxxx>
Subject: [fam] Re: [prepatch] Directory Notification
From: willy@xxxxxxxxxxxxxxxxxx
Date: Sun, 21 May 2000 16:07:51 -0400
Cc: linux-kernel@xxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxxx, tridge@xxxxxxxxxxxxx, fam@xxxxxxxxxxx
In-reply-to: <20000521121830.X28590@xxxxxxxxxxxxxxxxxx>; from willy@xxxxxxxxxxxxxxxxxx on Sun, May 21, 2000 at 12:18:30PM -0400
References: <20000519225041.P28590@xxxxxxxxxxxxxxxxxx> <200005201931.PAA07400@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20000521121830.X28590@xxxxxxxxxxxxxxxxxx>
Sender: owner-fam@xxxxxxxxxxx
On Sun, May 21, 2000 at 12:18:30PM -0400, willy@xxxxxxxxxxxxxxxxxx wrote:
> There are really 4 conflated patches here:
> 
>  * A rewrite of the fs/locks.c code.
>  * Making kill_fasync() SMP-safe.
>  * Directory notification.
>  * Addition of file leases.
> 
> I should split them up.

ftp://ftp.uk.linux.org/pub/linux/people/willy/2.3.99pre8/

dirnot.diff requires killfasync.diff to be applied first, but it's not
relevant to understanding the patches.  I just split the patches up by
hand, there may well be duplicated pieces or poor line numbering.  As I
suspect the lock-rewrite patch is by far the biggest chunk; it includes
the leases.  Trond, I haven't fixed any of the problems you noticed yet,
you needn't bother looking.

--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>