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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SN6PR04MB46409E525B4AA66C428122EEFCA80@SN6PR04MB4640.namprd04.prod.outlook.com>
Date:   Sat, 2 May 2020 16:19:17 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     Bean Huo <huobean@...il.com>, Bart Van Assche <bvanassche@....org>,
        "alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
        "asutoshd@...eaurora.org" <asutoshd@...eaurora.org>,
        "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>,
        "stanley.chu@...iatek.com" <stanley.chu@...iatek.com>,
        "beanhuo@...ron.com" <beanhuo@...ron.com>,
        "tomas.winkler@...el.com" <tomas.winkler@...el.com>,
        "cang@...eaurora.org" <cang@...eaurora.org>
CC:     "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 5/5] scsi: ufs: UFS Host Performance Booster(HPB)
 driver

Hi Bean,

> To me, hierarchical design sounds good, and move the implementation of
> HPB manager module to SCSI layer is nice. but what is opinion of
> others? and which way they prefer. or they want us to continue current
> Samsung approach and solve its cons further.
I can put an RFC together in few days.
My plan is to borrow as much as possible from Samsung driver,
But to move the L2P cache management and HPB-READ command setup to the scsi mid-layer.
Also maybe elaborate the host-managed mode logic to some extent.
This will not be a full-fledged driver, but more of a skeleton - 
The gory details can come after, once we'll agree on the general concept.

Let's wait few  days more to allow some more people to comment.
Ideally, this should be a joint effort of the ufs community,
Given the size of this driver, and the  industry's interest and focus.

Thanks,
Avri

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ