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>] [day] [month] [year] [list]
Message-ID: <20161209003611.GA4661@jagdpanzerIV.localdomain>
Date:   Fri, 9 Dec 2016 09:36:11 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To:     Cory Pruce <corypruce@...il.com>
Cc:     Nitin Gupta <nitingupta910@...il.com>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
        linux-kernel@...r.kernel.org, minchan@...nel.org
Subject: Re: ZRAM struct disk usage

On (12/08/16 11:17), Cory Pruce wrote:
>    Just wondering if it was really necessary to use the disk struct. It seems
>    like the struct is more used for record keeping/io config than actually
>    holding the data (actual data is worked with via page operations).
> 
>    Is this correct? What was the main need to use the data structure? I see
>    that the one and only partition is used for io acct but this seems more
>    nice to have to me than truly necessary being that this isn't an actual
>    peripheral.

because we want to have an actual block device with disk capacity,
device IO request queue and so no.

	-ss

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ