On Wed, 2014-01-22 at 15:19 +-0000, Mel Gorman wrote: +AD4- On Wed, Jan 22, 2014 at 09:58:46AM -0500, Ric Wheeler wrote: +AD4- +AD4- On 01/22/2014 09:34 AM, Mel Gorman wrote: +AD4- +AD4- +AD4-On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote: +AD4- +AD4- +AD4APg-On 01/22/2014 04:34 AM, Mel Gorman wrote: +AD4- +AD4- +AD4APgA+-On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote: +AD4- +AD4- +AD4APgA+AD4-One topic that has been lurking forever at the edges is the current +AD4- +AD4- +AD4APgA+AD4-4k limitation for file system block sizes. Some devices in +AD4- +AD4- +AD4APgA+AD4-production today and others coming soon have larger sectors and it +AD4- +AD4- +AD4APgA+AD4-would be interesting to see if it is time to poke at this topic +AD4- +AD4- +AD4APgA+AD4-again. +AD4- +AD4- +AD4APgA+AD4- +AD4- +AD4- +AD4APgA+-Large block support was proposed years ago by Christoph Lameter +AD4- +AD4- +AD4APgA+-(http://lwn.net/Articles/232757/). I think I was just getting started +AD4- +AD4- +AD4APgA+-in the community at the time so I do not recall any of the details. I do +AD4- +AD4- +AD4APgA+-believe it motivated an alternative by Nick Piggin called fsblock though +AD4- +AD4- +AD4APgA+-(http://lwn.net/Articles/321390/). At the very least it would be nice to +AD4- +AD4- +AD4APgA+-know why neither were never merged for those of us that were not around +AD4- +AD4- +AD4APgA+-at the time and who may not have the chance to dive through mailing list +AD4- +AD4- +AD4APgA+-archives between now and March. +AD4- +AD4- +AD4APgA+- +AD4- +AD4- +AD4APgA+-FWIW, I would expect that a show-stopper for any proposal is requiring +AD4- +AD4- +AD4APgA+-high-order allocations to succeed for the system to behave correctly. +AD4- +AD4- +AD4APgA+- +AD4- +AD4- +AD4APg-I have a somewhat hazy memory of Andrew warning us that touching +AD4- +AD4- +AD4APg-this code takes us into dark and scary places. +AD4- +AD4- +AD4APg- +AD4- +AD4- +AD4-That is a light summary. As Andrew tends to reject patches with poor +AD4- +AD4- +AD4-documentation in case we forget the details in 6 months, I'm going to guess +AD4- +AD4- +AD4-that he does not remember the details of a discussion from 7ish years ago. +AD4- +AD4- +AD4-This is where Andrew swoops in with a dazzling display of his eidetic +AD4- +AD4- +AD4-memory just to prove me wrong. +AD4- +AD4- +AD4- +AD4- +AD4- +AD4-Ric, are there any storage vendor that is pushing for this right now? +AD4- +AD4- +AD4-Is someone working on this right now or planning to? If they are, have they +AD4- +AD4- +AD4-looked into the history of fsblock (Nick) and large block support (Christoph) +AD4- +AD4- +AD4-to see if they are candidates for forward porting or reimplementation? +AD4- +AD4- +AD4-I ask because without that person there is a risk that the discussion +AD4- +AD4- +AD4-will go as follows +AD4- +AD4- +AD4- +AD4- +AD4- +AD4-Topic leader: Does anyone have an objection to supporting larger block +AD4- +AD4- +AD4- sizes than the page size? +AD4- +AD4- +AD4-Room: Send patches and we'll talk. +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- I will have to see if I can get a storage vendor to make a public +AD4- +AD4- statement, but there are vendors hoping to see this land in Linux in +AD4- +AD4- the next few years. +AD4- +AD4- What about the second and third questions -- is someone working on this +AD4- right now or planning to? Have they looked into the history of fsblock +AD4- (Nick) and large block support (Christoph) to see if they are candidates +AD4- for forward porting or reimplementation? I really think that if we want to make progress on this one, we need code and someone that owns it. Nick's work was impressive, but it was mostly there for getting rid of buffer heads. If we have a device that needs it and someone working to enable that device, we'll go forward much faster. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
