From: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: pid namespace .text overhead
Date: Tue, 11 Sep 2007 08:36:08 -0700 [thread overview]
Message-ID: <1189524968.17236.18.camel@localhost> (raw)
In-Reply-To: <20070911020406.GA31721-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Mon, 2007-09-10 at 19:04 -0700, sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org wrote:
>
> Thats a good point.
>
> We have been a bit liberal with "inline" given that lot of the code
> was
> going to affect the "fast-path" clone().
>
> Should we shoot for a time/space trade-off or can we make some inlines
> conditional (i.e inline when not configured for say embedded linux) ?
Can we make them switch somehow on -Os? That's what the embedded guys
use.
-- Dave
prev parent reply other threads:[~2007-09-11 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 19:38 pid namespace .text overhead Cedric Le Goater
[not found] ` <46E59D2B.7030609-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-09-11 2:04 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
[not found] ` <20070911020406.GA31721-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-11 7:13 ` Cedric Le Goater
2007-09-11 15:36 ` Dave Hansen [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=1189524968.17236.18.camel@localhost \
--to=haveblue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.