From: Eric Sandeen <sandeen@redhat.com> To: Beata Michalska <b.michalska@samsung.com>, linux-kernel@vger.kernel.org Cc: tytso@mit.edu, adilger.kernel@dilger.ca, hughd@google.com, lczerner@redhat.com, hch@infradead.org, linux-ext4@vger.kernel.org, linux-mm@kvack.org, kyungmin.park@samsung.com, kmpark@infradead.org Subject: Re: [RFC 1/4] fs: Add generic file system event notifications Date: Wed, 15 Apr 2015 22:46:23 -0500 [thread overview] Message-ID: <552F308F.1050505@redhat.com> (raw) In-Reply-To: <1429082147-4151-2-git-send-email-b.michalska@samsung.com> On 4/15/15 2:15 AM, Beata Michalska wrote: > Introduce configurable generic interface for file > system-wide event notifications to provide file > systems with a common way of reporting any potential > issues as they emerge. > > The notifications are to be issued through generic > netlink interface, by a dedicated, for file system > events, multicast group. The file systems might as > well use this group to send their own custom messages. ... > + 4.3 Threshold notifications: > + > + #include <linux/fs_event.h> > + void fs_event_alloc_space(struct super_block *sb, u64 ncount); > + void fs_event_free_space(struct super_block *sb, u64 ncount); > + > + Each filesystme supporting the treshold notifiactions should call > + fs_event_alloc_space/fs_event_free_space repsectively whenever the > + ammount of availbale blocks changes. > + - sb: the filesystem's super block > + - ncount: number of blocks being acquired/released so: > +void fs_event_alloc_space(struct super_block *sb, u64 ncount) > +{ > + struct fs_trace_entry *en; > + s64 count; > + > + spin_lock(&fs_trace_lock); Every allocation/free for every supported filesystem system-wide will be serialized on this global spinlock? That sounds like a non-starter... -Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@redhat.com> To: Beata Michalska <b.michalska@samsung.com>, linux-kernel@vger.kernel.org Cc: tytso@mit.edu, adilger.kernel@dilger.ca, hughd@google.com, lczerner@redhat.com, hch@infradead.org, linux-ext4@vger.kernel.org, linux-mm@kvack.org, kyungmin.park@samsung.com, kmpark@infradead.org Subject: Re: [RFC 1/4] fs: Add generic file system event notifications Date: Wed, 15 Apr 2015 22:46:23 -0500 [thread overview] Message-ID: <552F308F.1050505@redhat.com> (raw) In-Reply-To: <1429082147-4151-2-git-send-email-b.michalska@samsung.com> On 4/15/15 2:15 AM, Beata Michalska wrote: > Introduce configurable generic interface for file > system-wide event notifications to provide file > systems with a common way of reporting any potential > issues as they emerge. > > The notifications are to be issued through generic > netlink interface, by a dedicated, for file system > events, multicast group. The file systems might as > well use this group to send their own custom messages. ... > + 4.3 Threshold notifications: > + > + #include <linux/fs_event.h> > + void fs_event_alloc_space(struct super_block *sb, u64 ncount); > + void fs_event_free_space(struct super_block *sb, u64 ncount); > + > + Each filesystme supporting the treshold notifiactions should call > + fs_event_alloc_space/fs_event_free_space repsectively whenever the > + ammount of availbale blocks changes. > + - sb: the filesystem's super block > + - ncount: number of blocks being acquired/released so: > +void fs_event_alloc_space(struct super_block *sb, u64 ncount) > +{ > + struct fs_trace_entry *en; > + s64 count; > + > + spin_lock(&fs_trace_lock); Every allocation/free for every supported filesystem system-wide will be serialized on this global spinlock? That sounds like a non-starter... -Eric -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-16 3:47 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-15 7:15 [RFC 0/4] Generic file system events interface Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 7:15 ` [RFC 1/4] fs: Add generic file system event notifications Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 19:25 ` Darrick J. Wong 2015-04-15 19:25 ` Darrick J. Wong 2015-04-16 8:22 ` Beata Michalska 2015-04-16 8:22 ` Beata Michalska 2015-04-17 8:48 ` Jan Kara 2015-04-17 8:48 ` Jan Kara 2015-04-16 3:46 ` Eric Sandeen [this message] 2015-04-16 3:46 ` Eric Sandeen 2015-04-16 8:41 ` Beata Michalska 2015-04-16 8:41 ` Beata Michalska 2015-04-16 20:10 ` Hugh Dickins 2015-04-16 20:10 ` Hugh Dickins 2015-04-17 9:10 ` Beata Michalska 2015-04-17 9:10 ` Beata Michalska 2015-04-16 21:56 ` Heinrich Schuchardt 2015-04-16 21:56 ` Heinrich Schuchardt 2015-04-17 9:46 ` Beata Michalska 2015-04-17 9:46 ` Beata Michalska 2015-04-17 9:46 ` Beata Michalska 2015-04-17 11:58 ` Jan Kara 2015-04-17 11:58 ` Jan Kara 2015-04-17 11:31 ` Jan Kara 2015-04-17 11:31 ` Jan Kara 2015-04-17 13:04 ` Beata Michalska 2015-04-17 13:04 ` Beata Michalska 2015-04-17 13:15 ` Beata Michalska 2015-04-17 13:15 ` Beata Michalska 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:16 ` Jan Kara 2015-04-17 13:23 ` Austin S Hemmelgarn 2015-04-17 13:41 ` Jan Kara 2015-04-17 13:41 ` Jan Kara 2015-04-17 14:51 ` John Spray 2015-04-17 14:51 ` John Spray 2015-04-17 15:43 ` Jan Kara 2015-04-17 15:43 ` Jan Kara 2015-04-17 16:08 ` John Spray 2015-04-17 16:08 ` John Spray 2015-04-17 16:08 ` John Spray 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:22 ` Jan Kara 2015-04-17 16:29 ` Austin S Hemmelgarn 2015-04-17 16:39 ` Jan Kara 2015-04-17 16:39 ` Jan Kara 2015-04-17 16:39 ` Jan Kara 2015-04-17 17:37 ` John Spray 2015-04-17 17:37 ` John Spray 2015-04-17 22:37 ` Andreas Dilger 2015-04-17 22:37 ` Andreas Dilger 2015-04-17 16:25 ` Beata Michalska 2015-04-17 16:25 ` Beata Michalska 2015-04-17 16:25 ` Beata Michalska 2015-04-17 22:44 ` Andreas Dilger 2015-04-17 22:44 ` Andreas Dilger 2015-04-20 8:56 ` Beata Michalska 2015-04-20 8:56 ` Beata Michalska 2015-04-20 10:32 ` Jan Kara 2015-04-20 10:32 ` Jan Kara 2015-04-15 7:15 ` [RFC 2/4] ext4: Add helper function to mark group as corrupted Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 7:15 ` [RFC 3/4] ext4: Add support for generic FS events Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-15 19:18 ` Darrick J. Wong 2015-04-15 19:18 ` Darrick J. Wong 2015-04-16 8:02 ` Beata Michalska 2015-04-16 8:02 ` Beata Michalska 2015-04-15 7:15 ` [RFC 4/4] shmem: " Beata Michalska 2015-04-15 7:15 ` Beata Michalska 2015-04-17 8:17 ` [RFC 0/4] Generic file system events interface Jan Kara 2015-04-17 8:17 ` Jan Kara 2015-04-17 9:10 ` Beata Michalska 2015-04-17 9:10 ` Beata Michalska
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=552F308F.1050505@redhat.com \ --to=sandeen@redhat.com \ --cc=adilger.kernel@dilger.ca \ --cc=b.michalska@samsung.com \ --cc=hch@infradead.org \ --cc=hughd@google.com \ --cc=kmpark@infradead.org \ --cc=kyungmin.park@samsung.com \ --cc=lczerner@redhat.com \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=tytso@mit.edu \ /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: linkBe 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.