All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Kevin McKinney <klmckinney1@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Change PAGE_SIZE from minimum 4k to 12k
Date: Thu, 25 May 2017 21:08:55 +0100	[thread overview]
Message-ID: <20170525210855.3ca03356@alans-desktop> (raw)
In-Reply-To: <20170525170526.GD3085@amd>

On Thu, 25 May 2017 19:05:26 +0200
Pavel Machek <pavel@ucw.cz> wrote:

> On Tue 2017-05-16 11:27:08, Kevin McKinney wrote:
> > Hi Everyone,
> > 
> > Would it be possible to have a custom block device driver read/write
> > in increments of 12k instead of reading/writing data in 4k increments?
> > In other words, I would like to change the default page size on a
> > x86_64 platform (4.4.0 kernel) from 4k to 12k as the minimum page
> > size?  I understand I may have negative performance due to
> > fragmentation. Any help would be appreciated.
> > 
> > If this is the wrong mailing list, please let me know the right one to use.  
> 
> I won't say "no" but ammount of work neccessary is likely measured in
> man-years. Plus, hardware page size _is_ 4KB.

Or a few other much larger sizes. Not that it actually matters. You can
implement a larger software page size for a platform but it would still
neeed to be a power of two, and you'd have trouble running some existing
binaries for x86.

What problem are you *actually* trying to solve ?

Alan

  reply	other threads:[~2017-05-25 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 15:27 Change PAGE_SIZE from minimum 4k to 12k Kevin McKinney
2017-05-16 16:46 ` Lennart Sorensen
2017-05-25 17:05 ` Pavel Machek
2017-05-25 20:08   ` Alan Cox [this message]
2017-05-25 21:02     ` Kevin McKinney
2017-05-25 21:55       ` Pavel Machek
2017-05-26 13:14         ` Kevin McKinney

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=20170525210855.3ca03356@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=klmckinney1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.