[<prev] [next>] [day] [month] [year] [list]
Message-ID: <24430.1567804750@warthog.procyon.org.uk>
Date: Fri, 06 Sep 2019 22:19:10 +0100
From: David Howells <dhowells@...hat.com>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: dhowells@...hat.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Whitehouse <swhiteho@...hat.com>,
Ray Strode <rstrode@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>, raven@...maw.net,
keyrings@...r.kernel.org, linux-usb@...r.kernel.org,
linux-block <linux-block@...r.kernel.org>,
Christian Brauner <christian@...uner.io>,
LSM List <linux-security-module@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Ray, Debarshi" <debarshi.ray@...il.com>,
Robbie Harwood <rharwood@...hat.com>
Subject: Re: Why add the general notification queue and its sources
Theodore Y. Ts'o <tytso@....edu> wrote:
> Something else which we should consider up front is how to handle the
> case where you have multiple userspace processes that want to
> subscribe to the same notification.
I have that.
> This also implies that we'll need to have some kind of standard header
> at the beginning to specify the source of a particular notification
> message.
That too.
David
Powered by blists - more mailing lists