From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, ck@vds.kolivas.org, pj@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Implement Swap Prefetching v23
Date: Fri, 10 Feb 2006 16:48:01 +1100 [thread overview]
Message-ID: <200602101648.01923.kernel@kolivas.org> (raw)
In-Reply-To: <43EC281B.2030000@yahoo.com.au>
On Friday 10 February 2006 16:43, Nick Piggin wrote:
> Con Kolivas wrote:
> > On Friday 10 February 2006 16:32, Nick Piggin wrote:
> >>Con Kolivas wrote:
> >>>Just so it's clear I understand, is this what you (both) had in mind?
> >>>Inline so it's not built for !CONFIG_SWAP_PREFETCH
> >>
> >>Close...
> >>
> >>>+inline void lru_cache_add_tail(struct page *page)
> >>
> >>Is this inline going to do what you intend?
> >
> > I don't care if it's actually inlined, but the subtleties of compilers is
> > way beyond me. All it positively achieves is silencing the unused
> > function warning so I had hoped it meant that function was not built. I
> > tend to be wrong though...
>
> I don't think it can because it is not used in the same file.
> You'd have to put it into the header file.
Yes that was the stream of "unimplemented" errors we started seeing on new
gccs that couldn't inline and said so. The build process is mystical and
somewhat random in order but I guessed if it encounters this first it should
be able to inline it. However as I said I don't really need it inlined.
> Not sure why it silences the unused function warning.
It probably just fools it... Will probably warn on newer gccs soon.
> You didn't
> replace a 'static' with the inline? I don't think there is any
> other way the compiler can know the function isn't used externally.
Well I could always just put it in a header file under CONFIG_SWAP_PREFETCH..
I was trying to do the swap.c thing that akpm suggested though.
Cheers,
Con
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-02-10 5:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 2:55 Con Kolivas
2006-02-10 3:25 ` Andrew Morton
2006-02-10 3:49 ` Con Kolivas
2006-02-10 4:07 ` Nick Piggin
2006-02-10 4:14 ` Con Kolivas
2006-02-10 4:17 ` Nick Piggin
2006-02-10 4:25 ` Andrew Morton
2006-02-10 4:45 ` Nick Piggin
2006-02-10 4:55 ` Andrew Morton
2006-02-10 5:01 ` Nick Piggin
2006-02-10 5:26 ` Con Kolivas
2006-02-10 5:32 ` Nick Piggin
2006-02-10 5:37 ` Con Kolivas
2006-02-10 5:43 ` Nick Piggin
2006-02-10 5:48 ` Con Kolivas [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=200602101648.01923.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.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