From: Mike Frysinger <vapier.adi@gmail.com>
To: "David VomLehn (dvomlehn)" <dvomlehn@cisco.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Russell King <rmk@arm.linux.org.uk>,
James.Bottomley@hansenpartnership.com,
linux-arch@vger.kernel.org, linux-embedded@vger.kernel.org,
ksummit-2009-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-2009-discuss] Representing Embedded Architectures at the Kernel Summit
Date: Wed, 3 Jun 2009 23:24:43 -0400 [thread overview]
Message-ID: <8bd0f97a0906032024k412ac3a5x1dbf52b74dc1ebbd@mail.gmail.com> (raw)
In-Reply-To: <FF038EB85946AA46B18DFEE6E6F8A2890151520C@xmb-rtp-218.amer.cisco.com>
On Wed, Jun 3, 2009 at 23:11, David VomLehn (dvomlehn) wrote:
> David Delaney has a proof-of-concept of an idea of his which was
> presented at the last CELF, which is basically to put the kernel and
> loadable kernel modules closely enough together that you can avoid the
> use of long jumps. He sees a better than 1% improvement in performance,
> which we've duplicated using a slightly different approach. This is nice
> payback for little work and, though it doesn't help on all processors,
> it helps on several.
it would help on the Blackfin architecture. we compile all kernel
modules with -mlong-call because of this issue.
> The problem is: how do you allocate memory with the magical "close to
> the kernel" attribute? We have something that adds a new ZONE_KERNEL
> (this name has some problems, actually). It seems like a pretty good
> solution if you look at zones as conceptually concentric usages, but
> with the current zone implementation, each zone must be contiguous. So,
> if we're talking about changing what zones are done, I'd like to throw
> this into the pot.
what do you do if the alloc fails ? return back to userspace with
something like ENOMEM and have it retry with a module that was
compiled with -mlong-call ?
-mike
next prev parent reply other threads:[~2009-06-04 3:24 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 15:22 Representing Embedded Architectures at the Kernel Summit James Bottomley
2009-06-02 17:29 ` Josh Boyer
2009-06-02 17:42 ` James Bottomley
2009-06-02 17:52 ` David VomLehn
2009-06-02 18:25 ` James Bottomley
2009-06-02 18:51 ` Josh Boyer
2009-06-02 19:30 ` Tim Bird
2009-06-02 20:37 ` [Ksummit-2009-discuss] " James Bottomley
2009-06-02 20:44 ` Bill Gatliff
2009-06-02 21:34 ` Robert Schwebel
2009-06-03 3:35 ` Greg KH
[not found] ` <20090731152617.GW29245@pengutronix.de>
2009-07-31 15:53 ` flicker free booting Robert Schwebel
2009-07-31 18:03 ` David VomLehn
2009-07-31 18:09 ` Robert Schwebel
2009-07-31 18:42 ` Bill Gatliff
2009-08-03 8:19 ` Sascha Hauer
2009-08-03 8:37 ` Geert Uytterhoeven
2009-07-31 18:46 ` Bill Gatliff
2009-07-31 19:48 ` Tim Bird
2009-07-31 19:51 ` Bill Gatliff
2009-07-31 20:05 ` Robert Schwebel
2009-08-01 1:26 ` Tim Bird
2009-07-31 19:25 ` Bill Gatliff
2009-08-01 14:25 ` Jamie Lokier
2009-06-03 0:03 ` [Ksummit-2009-discuss] Representing Embedded Architectures at the Kernel Summit David VomLehn
2009-06-03 0:52 ` Eric W. Biederman
2009-06-03 1:42 ` Steven Rostedt
2009-06-02 22:21 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 6:24 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-10 23:13 ` Kumar Gala
2009-06-14 3:48 ` Grant Likely
2009-06-10 23:08 ` Kumar Gala
2009-06-02 17:29 ` Grant Likely
2009-06-02 17:45 ` David VomLehn
2009-06-02 18:46 ` Grant Likely
2009-06-02 17:48 ` James Bottomley
2009-06-03 12:17 ` Mark Brown
2009-06-04 18:18 ` Grant Likely
2009-06-02 21:10 ` Russell King
2009-06-02 21:16 ` Bill Gatliff
2009-06-02 21:18 ` Geert Uytterhoeven
2009-06-02 21:40 ` Robert Schwebel
[not found] ` <20090602214005.GL32630@pengutronix.de>
2009-06-02 21:48 ` Russell King
[not found] ` <10f740e80906021418i1d58f5eer940e7a8ec9fb8b9e@mail.gmail.com>
2009-06-03 7:07 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-04 20:08 ` Grant Likely
[not found] ` <4A2596B4.3020309@billgatliff.com>
2009-06-04 20:15 ` Grant Likely
[not found] ` <3340601010994331832@unknownmsgid>
2009-06-04 20:24 ` Grant Likely
2009-06-03 6:53 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-03 13:04 ` Catalin Marinas
2009-06-03 13:18 ` Josh Boyer
2009-06-03 13:45 ` Catalin Marinas
2009-06-03 14:11 ` Josh Boyer
2009-06-03 14:06 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 16:19 ` James Bottomley
2009-06-03 17:09 ` Russell King
2009-06-03 18:43 ` Andrew Morton
2009-06-03 19:01 ` James Bottomley
2009-06-04 3:11 ` David VomLehn (dvomlehn)
2009-06-04 3:24 ` Mike Frysinger [this message]
2009-06-04 9:23 ` Mel Gorman
2009-06-03 19:08 ` Catalin Marinas
2009-06-10 9:42 ` Thomas Petazzoni
2009-06-16 6:42 ` Mike Rapoport
2009-06-16 8:06 ` Mike Frysinger
2009-06-16 12:19 ` [Ksummit-2009-discuss] " Ralf Baechle
2009-06-17 4:26 ` H. Peter Anvin
2009-06-17 15:04 ` Ralf Baechle
2009-06-17 17:14 ` H. Peter Anvin
2009-06-16 16:06 ` Grant Likely
2009-06-16 18:18 ` Jamie Lokier
2009-06-16 19:28 ` Grant Likely
2009-06-16 20:07 ` Jamie Lokier
2009-06-16 20:10 ` Marcel Holtmann
2009-06-16 21:04 ` Grant Likely
2009-06-18 3:05 ` Paul Mundt
2009-06-17 14:31 ` Kumar Gala
2009-06-18 2:51 ` Paul Mundt
2009-06-19 2:59 ` Kumar Gala
2009-06-19 3:00 ` Paul Mundt
2009-06-19 7:53 ` Kumar Gala
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=8bd0f97a0906032024k412ac3a5x1dbf52b74dc1ebbd@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dvomlehn@cisco.com \
--cc=ksummit-2009-discuss@lists.linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).