From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Matt Mackall <mpm@selenic.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Avoiding fragmentation through different allocator
Date: Thu, 13 Jan 2005 02:20:01 -0500 [thread overview]
Message-ID: <1105600801.11555.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050113070314.GL2995@waste.org>
on den 12.01.2005 Klokka 23:03 (-0800) skreiv Matt Mackall:
> You might stress higher order page allocation with a) 8k stacks turned
> on b) UDP NFS with large read/write.
b) Unless your network uses jumbo frames, UDP NFS should not be doing
higher order page allocation.
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-01-13 7:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:09 Mel Gorman
2005-01-13 7:03 ` Matt Mackall
2005-01-13 7:20 ` Trond Myklebust [this message]
2005-01-13 10:22 ` Mel Gorman
2005-01-13 7:31 ` William Lee Irwin III
2005-01-13 10:11 ` Mel Gorman
2005-01-14 21:42 ` Marcelo Tosatti
2005-01-15 1:31 ` William Lee Irwin III
2005-01-15 19:19 ` Mel Gorman
2005-01-12 22:45 Tolentino, Matthew E
2005-01-12 23:12 ` Mel Gorman
2005-01-13 8:02 ` Hirokazu Takahashi
2005-01-13 10:27 ` Mel Gorman
2005-01-16 4:03 ` Yasunori Goto
2005-01-16 16:21 ` Mel Gorman
2005-01-17 23:08 ` Yasunori Goto
2005-01-19 13:45 ` Mel Gorman
2005-01-17 16:48 Tolentino, Matthew E
2005-01-19 13:17 ` Mel Gorman
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=1105600801.11555.6.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mpm@selenic.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