lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 May 2019 07:27:19 -0700 From: 'Christoph Hellwig' <hch@...radead.org> To: kanchan <joshi.k@...sung.com> Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org, linux-nvme@...ts.infradead.org, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, prakash.v@...sung.com, anshul@...sung.com, "Martin K. Petersen" <martin.petersen@...cle.com> Subject: Re: [PATCH v5 0/7] Extend write-hint framework, and add write-hint for Ext4 journal On Fri, May 17, 2019 at 11:01:55AM +0530, kanchan wrote: > Sorry but can you please elaborate the issue? I do not get what is being > statically allocated which was globally available earlier. > If you are referring to nvme driver, available streams at subsystem level > are being reflected for all namespaces. This is same as earlier. > There is no attempt to explicitly allocate (using dir-receive) or reserve > streams for any namespace. > Streams will continue to get allocated/released implicitly as and when > writes (with stream id) arrive. We have made a concious decision that we do not want to expose streams as an awkward not fish not flesh interface, but instead life time hints. I see no reason to change from and burden the whole streams complexity on other in-kernel callers.
Powered by blists - more mailing lists