public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [RFC][PATCH] zram: drop partial_io support
Date: Wed, 16 Dec 2015 10:29:09 +0900	[thread overview]
Message-ID: <20151216012909.GB575@swordfish> (raw)
In-Reply-To: <20151216010106.GA12679@bbox>

Hello Minchan,

On (12/16/15 10:01), Minchan Kim wrote:
> Hello Sergey,
> 
> Sorry for the late response. I am in long vavacation now but today,
> I get small time to sit down on computer. :)

Have a good one!

> On Mon, Dec 14, 2015 at 09:38:55PM +0900, Sergey Senozhatsky wrote:
> > Hello,
> > 
> > I've been thinking about this for some time, but didn't have a chance
> > to properly investigate so far. My question is: why do we even bother
> > with partial IO in zram?
> 
> It was done before I involved zram actively so I should spend a time
> to search the reason.

Thanks a lot! I appreciate this. I was about to do the same but still
a bit too busy.

> Firstly, author was Jerome.
> http://lists.openwall.net/linux-kernel/2011/06/10/318
> 
> And Nitin wanted to increase logical block size 64K instead of
> making complex part by partial I/O.
> http://lists.openwall.net/linux-kernel/2011/06/10/402
> 
> And Jeff and Martin said there is no problem to increase
> logical_block_size from unsigned short if people are aware of
> the implications bigger blocks have on the filesystems they put on top.
> 
> http://lists.openwall.net/linux-kernel/2011/06/14/289
> http://lists.openwall.net/linux-kernel/2011/06/14/324
> 
> Jerome finally found severe problem which FAT fs are unable to
> cope with 64K logical blocks at least.
> http://lists.openwall.net/linux-kernel/2011/07/01/196
>
> That's why Nitin decided to suppport partial IO in zram.
> And I think it does make sense.

uhhh... ok, I see. Thanks.

	-ss

      reply	other threads:[~2015-12-16  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 12:38 [RFC][PATCH] zram: drop partial_io support Sergey Senozhatsky
2015-12-16  1:01 ` Minchan Kim
2015-12-16  1:29   ` Sergey Senozhatsky [this message]

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=20151216012909.GB575@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky@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