From mboxrd@z Thu Jan 1 00:00:00 1970 From: helen.koike@collabora.co.uk (Helen Koike) Date: Thu, 12 May 2016 01:05:32 -0300 Subject: [PATCH v2 RFC] nvme: improve performance for virtual NVMe devices In-Reply-To: <20160511174306.GB31047@localhost.localdomain> References: <1460657059-21214-1-git-send-email-helen.koike@collabora.co.uk> <5718D697.3050800@collabora.co.uk> <20160421133823.GA13563@infradead.org> <573362D1.3040401@collabora.co.uk> <20160511174306.GB31047@localhost.localdomain> Message-ID: <5734010C.5080800@collabora.co.uk> On 11-05-2016 14:43, Keith Busch wrote: > On Wed, May 11, 2016@01:50:25PM -0300, Helen Koike wrote: >> >> On 21-04-2016 10:38, Christoph Hellwig wrote: >>> I've not spent much time at it due to a busy conference week, but there >>> are two main comments on why I don't think this is suitable as is >>> despite really liking the general idea. >>> >>> - I'd really like this to be proposed as an official extension to the >>> NVMe technical workgroup. I'm also happy to help with making that >>> happen. I really don't like to merge it until we have some basic >>> agreement on it, although once the basic agreement is there it >>> shouldn't be too hard to also support the older google specific >>> version. And this is no new feedback, a couple of people including >>> me said that a long time ago, and we've seen zero action on it. >> >> >> How the process of submitting a proposal to the NVMe technical workgroup >> works? If it is just a matter of sending a document as the entry point and >> as you offered help, I was wondering if you could just forward this proposal >> to them and I can continue the work from that point onwards (as we wouldn't >> like to burden you), would that be possible? > > Are you a contributing member of the NVM Express organization? If so, > you directly send your proposal to the technical working group mailing > list to start the process without a middle-man. No, I am not, that is why I am asking. If it's not a burden to you I would appreciate some help to start the proposal with the NVMe technical workgroup, otherwise I'll need to go through a more bureaucratic path to do it in Google's name.