From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Cory Pruce <corypruce@gmail.com>
Cc: Nitin Gupta <nitingupta910@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, minchan@kernel.org
Subject: Re: ZRAM struct disk usage
Date: Fri, 9 Dec 2016 09:36:11 +0900 [thread overview]
Message-ID: <20161209003611.GA4661@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <CANOqyr43U0KiQECb5P7sUDpFd9q55vKJViPLaoxuGJEBgcf19Q@mail.gmail.com>
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
parent reply other threads:[~2016-12-09 0:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANOqyr43U0KiQECb5P7sUDpFd9q55vKJViPLaoxuGJEBgcf19Q@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161209003611.GA4661@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=corypruce@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=nitingupta910@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).