From: Eric Dumazet <dada1@cosmosbay.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RFC] non-refcounted pages, application to slab?
Date: Wed, 25 Jan 2006 10:54:08 +0100 [thread overview]
Message-ID: <43D74AC0.9020002@cosmosbay.com> (raw)
In-Reply-To: <20060125093909.GE32653@wotan.suse.de>
Nick Piggin a ecrit :
> @@ -2604,10 +2604,10 @@ static inline void *__cache_alloc(kmem_c
>
> local_irq_save(save_flags);
> objp = ____cache_alloc(cachep, flags);
> + prefetchw(objp);
> local_irq_restore(save_flags);
> objp = cache_alloc_debugcheck_after(cachep, flags, objp,
> __builtin_return_address(0));
> - prefetchw(objp);
> return objp;
> }
I'm not sure why you moved this prefetchw(obj) : This is not related to your
'non-refcounting' part, is it ?
When I added this prefetchw in slab code, I did place it *after* the
local_irq_restore(save_flags); because I was not sure if the
serialization/barrier (popf) would force the cpu (x86/x86_64 in mind) to either :
- finish all the loads (even if they are speculative/hints) (so giving a bad
latency)
- cancel the speculative loads (so prefetchw() *before* the
local_irq_restore() would be useless.
Thank you
Eric
--
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>
next prev parent reply other threads:[~2006-01-25 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:39 Nick Piggin
2006-01-25 9:54 ` Eric Dumazet [this message]
2006-01-25 9:56 ` Nick Piggin
2006-01-25 10:26 ` Eric Dumazet
2006-01-25 10:57 ` Nick Piggin
2006-01-25 11:10 ` Eric Dumazet
2006-01-25 11:18 ` Nick Piggin
2006-01-25 10:30 ` Pekka Enberg
2006-01-25 11:00 ` Nick Piggin
2006-01-25 11:19 ` Pekka Enberg
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=43D74AC0.9020002@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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