[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1401231450550.8031@nuc>
Date: Thu, 23 Jan 2014 14:54:37 -0600 (CST)
From: Christoph Lameter <cl@...ux.com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
cc: Dave Chinner <david@...morbit.com>, Chris Mason <clm@...com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"mgorman@...e.de" <mgorman@...e.de>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"lsf-pc@...ts.linux-foundation.org"
<lsf-pc@...ts.linux-foundation.org>,
"rwheeler@...hat.com" <rwheeler@...hat.com>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] really large storage sectors - going
beyond 4096 bytes
On Thu, 23 Jan 2014, James Bottomley wrote:
> If the compound page infrastructure exists today and is usable for this,
> what else do we need to do? ... because if it's a couple of trivial
> changes and a few minor patches to filesystems to take advantage of it,
> we might as well do it anyway. I was only objecting on the grounds that
> the last time we looked at it, it was major VM surgery. Can someone
> give a summary of how far we are away from being able to do this with
> the VM system today and what extra work is needed (and how big is this
> piece of work)?
The main problem for me was the page cache. The VM would not be such a
problem. Changing the page cache function required updates to many
filesystems.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists