Re: [00/17] Large Blocksize Support V3

On Thu, 26 Apr 2007, Eric W. Biederman wrote:

My most practical suggestion is to have support code so that you can
do all of the locking (that I/O cares about) on the first page of a
page group in the page cache. You don't need larger physical pages to
do that.

Virtual mappings for larger pages? Or some software simulated form? This
all sounds like awful hacks.

Iff we really the larger physical page size to support the hardware
then it makes sense to go down a path of larger pages. But it doesn't.

You are redefining the problem. We need larger physical sizes to support
the hardware. Yes. We can dodge the issue with shim layers and hacks. It
is obvious from the kernel sources that this is needed.

There is also a more fundamental reasons this patch is silly. It assumes
that there is a trivial mapping between filesystems (the primary target
of the page cache and blocks on disk). Now I admit this is common but
there is no reason to supposed it is true, and this patch appears to
exacerbate things.

The patch does the obvious... Nothing is silly about memory being
contigous in memory and on disk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: hard disk access on every keystroke in console mode!
    ... What speed memory? ... > booting single user in 80x25 text mode gives still gives me the hard disk ... since pre4 and there is a patch against 2.4.22) has a proc entry ... implementation though its disabled when laptop mode is not enabled, ...
    (Debian-User)
  • Re: Memory manager writing pages back to executables...
    ... intercept noncached paging reads from shell32.dll, and patch the buffer ... > those addresses into the kernel-mode area of the memory. ... > "Modified List" and thus will not be written to disk by the Modified ... Is it true that the memory manager will write pages back to the ...
    (microsoft.public.development.device.drivers)
  • Memory manager writing pages back to executables...
    ... He writes "Now that we know which addresses to patch, ... those addresses into the kernel-mode area of the memory. ... "Modified List" and thus will not be written to disk by the Modified ... Is it true that the memory manager will write pages back to the ...
    (microsoft.public.development.device.drivers)
  • Proposed Assembler Commands
    ... ACM Automatically Clear Memory ... BKCRDR Backspace Card Reader ... BKSPD Backspace Disk ... EIAO Execute In Any Order ...
    (sci.electronics.design)
  • Re: Att. Alex Nichol -VM cont.
    ... I find documentation that says a 4kb page in memory is written to the hard ... manner that a 4kb memory page is equal to a 4kb cluster written on the disk". ... So where is the basis for saying since 4kb paging in memory that 4kb clusters ...
    (microsoft.public.windowsxp.general)
Loading