From: "Dan Kruchinin" <dubalom@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: how to purposfully fragment memory?
Date: Wed, 21 Mar 2007 00:34:08 +0300 [thread overview]
Message-ID: <a8f16e2b0703201434w39108ed0m6d1b50f3b8cd6c42@mail.gmail.com> (raw)
In-Reply-To: <4600393C.8030401@nortel.com>
On 3/20/07, Chris Friesen <cfriesen@nortel.com> wrote:
> Asgard wrote:
>
> > btw, can you describe your aim in details?
>
> I'm doing some work on a network device driver. We were having jumbo
> frame issues after being up for a month or so because it couldn't
> allocate enough contiguous memory.
>
> We've got a new code path now that doesn't need large contiguous
> allocations, so I'd like to demonstrate it by forcing the system to
> become severely fragmented.
>
> Chris
>
and by the way, you can try to use void split_page(struct page *page,
unsigned int order) function, but keep in mind, that it's not
recommended to use it in drivers:
/*
* split_page takes a non-compound higher-order page, and splits it into
* n (1<<order) sub-pages: page[0..n]
* Each sub-page must be freed individually.
*
* Note: this is probably too low level an operation for use in drivers.
* Please consult with lkml before using this in your driver.
*/
void split_page(struct page *page, unsigned int order)
Good luck.
Dan.
prev parent reply other threads:[~2007-03-20 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 17:43 Chris Friesen
[not found] ` <a8f16e2b0703201215q78dfdd3du54c77be7c9d843e0@mail.gmail.com>
[not found] ` <4600393C.8030401@nortel.com>
2007-03-20 21:34 ` Dan Kruchinin [this message]
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=a8f16e2b0703201434w39108ed0m6d1b50f3b8cd6c42@mail.gmail.com \
--to=dubalom@gmail.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.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®