From: Andrew Morton <akpm@osdl.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: torvalds@osdl.org, arjan@infradead.org, dada1@cosmosbay.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 spinlocks should use the full 32 bits, not only 8 bits
Date: Thu, 20 Oct 2005 15:44:57 -0700 [thread overview]
Message-ID: <20051020154457.100b5565.akpm@osdl.org> (raw)
In-Reply-To: <20051020222703.GA28221@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
>
> +/*
> + * We inline the unlock functions in the nondebug case:
> + */
> +#if defined(CONFIG_DEBUG_SPINLOCK) || defined(CONFIG_PREEMPT)
> +# define spin_unlock(lock) _spin_unlock(lock)
> +# define read_unlock(lock) _read_unlock(lock)
> +# define write_unlock(lock) _write_unlock(lock)
> +#else
> +# define spin_unlock(lock) __raw_spin_unlock(&(lock)->raw_lock)
> +# define read_unlock(lock) __raw_read_unlock(&(lock)->raw_lock)
> +# define write_unlock(lock) __raw_write_unlock(&(lock)->raw_lock)
> +#endif
>
spin_lock is still uninlined.
static inline __attribute__((always_inline)) struct dentry *dget_parent(struct dentry *dentry)
{
struct dentry *ret;
_spin_lock(&dentry->d_lock);
ret = dget(dentry->d_parent);
__raw_spin_unlock(&(&dentry->d_lock)->raw_lock);
return ret;
}
as is spin_lock_irqsave() and spin_lock_irq()
uninlining spin_lock will probably increase overall text size, but mainly in
the out-of-line section.
<looks>
we removed the out-of-line section :(
read_lock is out-of-line. read_unlock is inlined
write_lock is out-of-line. write_unlock is out-of-line.
Needs work ;)
next prev parent reply other threads:[~2005-10-20 22:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 4:04 i386 spinlock fairness: bizarre test results Chuck Ebbert
2005-10-11 9:42 ` Eric Dumazet
2005-10-11 13:00 ` Alan Cox
2005-10-11 14:44 ` Linus Torvalds
2005-10-11 15:32 ` [PATCH] i386 spinlocks should use the full 32 bits, not only 8 bits Eric Dumazet
2005-10-11 16:03 ` Linus Torvalds
2005-10-11 16:36 ` Eric Dumazet
2005-10-11 16:54 ` Linus Torvalds
2005-10-11 16:55 ` Linus Torvalds
2005-10-17 7:03 ` Andrew Morton
2005-10-17 7:20 ` Arjan van de Ven
2005-10-20 21:50 ` Ingo Molnar
2005-10-20 21:57 ` Linus Torvalds
2005-10-20 22:02 ` Ingo Molnar
2005-10-20 22:15 ` Linus Torvalds
2005-10-20 22:27 ` Ingo Molnar
2005-10-20 22:44 ` Andrew Morton [this message]
2005-10-20 22:53 ` Ingo Molnar
2005-10-20 23:01 ` Andrew Morton
2005-10-20 23:26 ` Ingo Molnar
2005-10-27 16:54 ` Paul Jackson
2005-10-11 17:59 ` Andi Kleen
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=20051020154457.100b5565.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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
Powered by JetHome