From: Hugh Dickins <hugh@veritas.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Ben LaHaise <bcrl@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-mm@kvack.org
Subject: Re: [wip-PATCH] Re: Large PAGE_SIZE
Date: Mon, 9 Jul 2001 15:18:43 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.21.0107091426450.1282-100000@localhost.localdomain> (raw)
In-Reply-To: <3B49AE09.CE19FBAC@mandrakesoft.com>
On Mon, 9 Jul 2001, Jeff Garzik wrote:
> Hugh Dickins wrote:
> > On Sun, 8 Jul 2001, Ben LaHaise wrote:
> > >
> > > Hmmm, interesting. At present page cache sizes from PAGE_SIZE to
> > > 8*PAGE_SIZE are working here. Setting the shift to 4 or a 64KB page size
> > > results in the SCSI driver blowing up on io completion.
> >
> > I hit that limit too: I believe it comes from unsigned short b_size.
>
> That limit's not a big deal.. the limits in the lower-level disk drivers
> are what you start hitting...
Examples?
Limits below 64kB with some drivers we happen not to be using,
or limits >= 64kB we'd soon hit if we chose to do something about
unsigned short b_size (e.g. short sizes in the drivers own code)?
Limits in the disk drivers or limits in their firmware? If the limits
are in the drivers, then they're probably PAGE_SIZE limits which raising
PAGE_SIZE deals with automatically, but raising PAGE_CACHE_SIZE needs
more edits to get working.
(Whereas raising PAGE_SIZE needs edits where it's the vm_pgoff
MMAP_? MMU_? PTE_? VM_? SUB? PAGE_SIZE that's needed.)
Linus believes it would be no more than a few buggy drivers which would
impose such limits; I don't know, I took little notice of the instances
I didn't need to change in raising PAGE_SIZE.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-07-09 14:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 5:06 [wip-PATCH] rfi: PAGE_CACHE_SIZE suppoort Ben LaHaise
2001-07-05 5:55 ` Linus Torvalds
2001-07-05 16:45 ` Large PAGE_SIZE Hugh Dickins
2001-07-05 17:13 ` Linus Torvalds
2001-07-05 18:38 ` Hugh Dickins
2001-07-05 18:53 ` Linus Torvalds
2001-07-05 20:41 ` Ben LaHaise
2001-07-05 20:59 ` Hugh Dickins
2001-07-06 5:11 ` Linus Torvalds
2001-07-09 3:04 ` [wip-PATCH] " Ben LaHaise
2001-07-09 11:18 ` Hugh Dickins
2001-07-09 13:13 ` Jeff Garzik
2001-07-09 14:18 ` Hugh Dickins [this message]
2001-07-09 14:33 ` Jeff Garzik
2001-07-09 17:21 ` Hugh Dickins
2001-07-10 5:53 ` Ben LaHaise
2001-07-10 16:42 ` Hugh Dickins
2001-07-18 0:02 ` Hugh Dickins
2001-07-18 18:48 ` Hugh Dickins
2001-07-22 23:08 ` Hugh Dickins
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=Pine.LNX.4.21.0107091426450.1282-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=bcrl@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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