linux-kernel - RE: [RFC PATCH 3/5] scsi: ufs: Introduce HPB module

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <SN6PR04MB4640638EAF31B0E3D11256DBFC820@SN6PR04MB4640.namprd04.prod.outlook.com>
Date:   Tue, 9 Jun 2020 06:51:39 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     "daejun7.park@...sung.com" <daejun7.park@...sung.com>,
        ALIM AKHTAR <alim.akhtar@...sung.com>,
        "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>,
        "asutoshd@...eaurora.org" <asutoshd@...eaurora.org>,
        "beanhuo@...ron.com" <beanhuo@...ron.com>,
        "stanley.chu@...iatek.com" <stanley.chu@...iatek.com>,
        "cang@...eaurora.org" <cang@...eaurora.org>,
        "bvanassche@....org" <bvanassche@....org>,
        "tomas.winkler@...el.com" <tomas.winkler@...el.com>
CC:     "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Sang-yoon Oh <sangyoon.oh@...sung.com>,
        Sung-Jun Park <sungjun07.park@...sung.com>,
        yongmyung lee <ymhungry.lee@...sung.com>,
        Jinyoung CHOI <j-young.choi@...sung.com>,
        Adel Choi <adel.choi@...sung.com>,
        BoRam Shin <boram.shin@...sung.com>
Subject: RE: [RFC PATCH 3/5] scsi: ufs: Introduce HPB module

> > > +unsigned int ufshpb_host_map_kbytes = 1 * 1024;
> > > +module_param(ufshpb_host_map_kbytes, uint, 0644);
> > > +MODULE_PARM_DESC(ufshpb_host_map_kbytes,
> > > +        "ufshpb host mapping memory kilo-bytes for ufshpb memory-pool");
> > You should introduce this module parameter in the patch that uses it.
> OK, could you recommend good location of introducing message? At the
> patch letter or in the codes?
I think this module parameter makes its first appearance in patch 4/5 - so maybe there?

> 
> Thanks,
> Daejun