From: Antonio Vargas <wind@cocodriloo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Antonio Vargas <wind@cocodriloo.com>,
linux-kernel@vger.kernel.org, nicoya@apia.dhs.org
Subject: cow-ahead N pages for fault clustering
Date: Mon, 14 Apr 2003 20:32:51 +0200 [thread overview]
Message-ID: <20030414183251.GH14552@wind.cocodriloo.com> (raw)
In-Reply-To: <16700000.1050340965@[10.10.2.4]>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On Mon, Apr 14, 2003 at 10:22:46AM -0700, Martin J. Bligh wrote:
> >> Ah, you probably don't want to do that ... it's very expensive. Moreover,
> >> if you exec 2ns later, all the effort will be wasted ... and it's very
> >> hard to deterministically predict whether you'll exec or not (stupid
> >> UNIX semantics). Doing it lazily is probably best, and as to "nodes
> >> would not have to reference the memory from others" - you're still
> >> doing that, you're just batching it on the front end.
> >
> > True... What about a vma-level COW-ahead just like we have a file-level
> > read-ahead, then? I mean batching the COW at unCOW-because-of-write time.
>
> That'd be interesting ... and you can test that on a UP box, is not just
> NUMA. Depends on the workload quite heavily, I suspect.
>
> > btw, COW-ahead sound really silly :)
>
> Yeah. So be sure to call it that if it works out ... we need more things
> like that ;-) Moooooo.
What about the attached one? I'm compiling it right now to test in UML :)
[ snip fake-NUMA-on-SMP discussion ]
Greets, Antonio.
[-- Attachment #2: cow-ahead.patch --]
[-- Type: text/plain, Size: 1709 bytes --]
mm/memory.c | 32 ++++++++++++++++++++++++++++----
1 files changed, 28 insertions(+), 4 deletions(-)
diff -puN mm/memory.c~cow-ahead mm/memory.c
--- 25/mm/memory.c~cow-ahead Mon Apr 14 20:08:44 2003
+++ 25-wind/mm/memory.c Mon Apr 14 20:26:17 2003
@@ -1452,7 +1452,7 @@ static int do_file_page(struct mm_struct
*/
static inline int handle_pte_fault(struct mm_struct *mm,
struct vm_area_struct * vma, unsigned long address,
- int write_access, pte_t *pte, pmd_t *pmd)
+ int write_access, pte_t *pte, pmd_t *pmd, int *cowahead)
{
pte_t entry;
@@ -1471,8 +1471,11 @@ static inline int handle_pte_fault(struc
}
if (write_access) {
- if (!pte_write(entry))
+ if (!pte_write(entry)) {
+ if(!cowahead)
+ *cowahead = 1;
return do_wp_page(mm, vma, address, pte, pmd, entry);
+ }
entry = pte_mkdirty(entry);
}
@@ -1492,6 +1495,17 @@ int handle_mm_fault(struct mm_struct *mm
pgd_t *pgd;
pmd_t *pmd;
+ int cowahead, i;
+ int retval, x;
+
+ /*
+ * Implement cow-ahead: copy-on-write several
+ * pages when we fault one of them
+ */
+
+ i = cowahead = 0;
+
+do_cowahead:
__set_current_state(TASK_RUNNING);
pgd = pgd_offset(mm, address);
@@ -1509,8 +1523,18 @@ int handle_mm_fault(struct mm_struct *mm
if (pmd) {
pte_t * pte = pte_alloc_map(mm, pmd, address);
- if (pte)
- return handle_pte_fault(mm, vma, address, write_access, pte, pmd);
+ if (!pte) break;
+
+ x = handle_pte_fault(mm, vma, address, write_access, pte, pmd, cowahead);
+ if(!i) retval = x;
+
+ i++;
+ address += PAGE_SIZE;
+
+ if(!cowahead || i >= 0 || address >= vma->vm_end)
+ return retval;
+
+ goto do_cowahead;
}
spin_unlock(&mm->page_table_lock);
return VM_FAULT_OOM;
_
next prev parent reply other threads:[~2003-04-14 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 13:31 Quick question about hyper-threading (also some NUMA stuff) Timothy Miller
2003-04-14 14:55 ` Martin J. Bligh
2003-04-14 15:29 ` Antonio Vargas
2003-04-14 15:39 ` Martin J. Bligh
2003-04-14 15:57 ` Antonio Vargas
2003-04-14 16:24 ` Martin J. Bligh
2003-04-14 16:43 ` Antonio Vargas
2003-04-14 16:37 ` Martin J. Bligh
2003-04-14 17:14 ` Antonio Vargas
2003-04-14 17:22 ` Martin J. Bligh
2003-04-14 18:32 ` Antonio Vargas [this message]
2003-04-14 18:47 ` cow-ahead N pages for fault clustering Antonio Vargas
2003-04-15 5:49 ` Martin J. Bligh
2003-04-18 17:35 ` Antonio Vargas
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=20030414183251.GH14552@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nicoya@apia.dhs.org \
/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
all inboxes | Powered by JetHome®