mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Christoph Hellwig <hch@infradead.org>,
	ltt-dev@shafik.org, systemtap@sources.redhat.com,
	Douglas Niehaus <niehaus@eecs.ku.edu>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] local_t : Documentation
Date: Tue, 9 Jan 2007 23:41:00 +0100	[thread overview]
Message-ID: <20070109224100.GB6555@elf.ucw.cz> (raw)
In-Reply-To: <20070109031446.GA29426@Krystal>

Hi!

> > > These patches extend and standardise local_t operations on each architectures,
> > > allowing a rich set of atomic operations to be done on per-cpu data with
> > > minimal performance impact. On some architectures, there seems to be no
> > > difference between the SMP and UP operation (same memory barriers, same
> > > LOCking), local.h simply includes asm-generic/local.h, which removes duplicated
> > > code.
> > 
> > Could you provide some Documentation/? Knowing when local_t can be
> > used is kind-of important.
> 
> Hi Pavel,
> 
> Thanks for this appropriate comment. I totally agree that there is a need for
> documentation about how local_t variables should be used. Here is the patch
> that adds Documentation/local_ops.txt. Comments are welcome.

AFAICT this fails to mention... Is local_t as big as int? As big as
long? Or perhaps smaller because high bits may be needed for locking?

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2007-01-09 22:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  0:15 [PATCH 0/10] local_t : adding and standardising atomic primitives Mathieu Desnoyers
2006-12-21  0:20 ` [PATCH 1/10] local_t : architecture agnostic Mathieu Desnoyers
2006-12-21  0:21 ` [PATCH 2/10] local_t : alpha Mathieu Desnoyers
2006-12-21  0:22 ` [PATCH 3/10] local_t : i386 Mathieu Desnoyers
2006-12-21 19:44   ` [Ltt-dev] [PATCH 3/10] local_t : i386, local_add_return fix Mathieu Desnoyers
2006-12-21  0:23 ` [PATCH 4/10] local_t : ia64 Mathieu Desnoyers
2006-12-21  0:25 ` [PATCH 5/10] " Mathieu Desnoyers
2006-12-21 14:04   ` [Ltt-dev] [PATCH 5/10] local_t : MIPS Mathieu Desnoyers
2006-12-21  0:25 ` [PATCH 6/10] local_t : parisc Mathieu Desnoyers
2006-12-21  0:27 ` [PATCH 7/10] local_t : powerpc Mathieu Desnoyers
2006-12-21  3:34   ` [Ltt-dev] " Mathieu Desnoyers
2007-01-24  9:08   ` Paul Mackerras
2007-01-24 10:43     ` Gabriel Paubert
2007-01-24 17:00     ` Mathieu Desnoyers
2006-12-21  0:27 ` [PATCH 8/10] local_t : s390 Mathieu Desnoyers
2006-12-21  0:28 ` [PATCH 9/10] local_t : sparc64 Mathieu Desnoyers
2006-12-21  0:29 ` [PATCH 10/10] local_t : x86_64 Mathieu Desnoyers
2006-12-21 19:46   ` [Ltt-dev] [PATCH 10/10] local_t : x86_64 : local_add_return Mathieu Desnoyers
2006-12-23  9:33 ` [PATCH 0/10] local_t : adding and standardising atomic primitives Pavel Machek
2007-01-09  3:14   ` [PATCH] local_t : Documentation Mathieu Desnoyers
2007-01-09 21:01     ` Andrew Morton
2007-01-09 22:06       ` Mathieu Desnoyers
2007-01-09 22:11         ` Andrew Morton
2007-01-09 22:38       ` Pavel Machek
2007-01-09 22:41     ` Pavel Machek [this message]
2007-01-09 23:21       ` [PATCH] local_t : Documentation - update Mathieu Desnoyers
2007-01-09 23:45         ` Pavel Machek
2007-01-10  0:39           ` Mathieu Desnoyers
2007-01-10  1:06             ` [Ltt-dev] " Mathieu Desnoyers

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=20070109224100.GB6555@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mbligh@mbligh.org \
    --cc=mingo@redhat.com \
    --cc=niehaus@eecs.ku.edu \
    --cc=systemtap@sources.redhat.com \
    --cc=tglx@linutronix.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
all inboxes | Powered by JetHome®