All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [patch 1/3] add the fsblock layer
Date: Mon, 25 Jun 2007 17:19:43 +1000	[thread overview]
Message-ID: <467F6C8F.9040400@yahoo.com.au> (raw)
In-Reply-To: <p73fy4h5q3c.fsf@bingen.suse.de>

Andi Kleen wrote:
> Nick Piggin <npiggin@suse.de> writes:
> 
> 
> [haven't read everything, just commenting on something that caught my eye]
> 
> 
>>+struct fsblock {
>>+	atomic_t	count;
>>+	union {
>>+		struct {
>>+			unsigned long	flags; /* XXX: flags could be int for better packing */
> 
> 
> int is not supported by many architectures, but works on x86 at least.

Yeah, that would be nice. We could actually use this for buffer_head as well,
but saving 4% there isn't so important as saving 20% for fsblock :)


> Hmm, could define a macro DECLARE_ATOMIC_BITMAP(maxbit) that expands to the smallest
> possible type for each architecture. And a couple of ugly casts for set_bit et.al.
> but those could be also hidden in macros. Should be relatively easy to do.

Cool. It would probably be useful for other things as well.

-- 
SUSE Labs, Novell Inc.

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nick Piggin <npiggin@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [patch 1/3] add the fsblock layer
Date: Mon, 25 Jun 2007 17:19:43 +1000	[thread overview]
Message-ID: <467F6C8F.9040400@yahoo.com.au> (raw)
In-Reply-To: <p73fy4h5q3c.fsf@bingen.suse.de>

Andi Kleen wrote:
> Nick Piggin <npiggin@suse.de> writes:
> 
> 
> [haven't read everything, just commenting on something that caught my eye]
> 
> 
>>+struct fsblock {
>>+	atomic_t	count;
>>+	union {
>>+		struct {
>>+			unsigned long	flags; /* XXX: flags could be int for better packing */
> 
> 
> int is not supported by many architectures, but works on x86 at least.

Yeah, that would be nice. We could actually use this for buffer_head as well,
but saving 4% there isn't so important as saving 20% for fsblock :)


> Hmm, could define a macro DECLARE_ATOMIC_BITMAP(maxbit) that expands to the smallest
> possible type for each architecture. And a couple of ugly casts for set_bit et.al.
> but those could be also hidden in macros. Should be relatively easy to do.

Cool. It would probably be useful for other things as well.

-- 
SUSE Labs, Novell Inc.

--
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>

  parent reply	other threads:[~2007-06-25  7:19 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-24  1:45 [RFC] fsblock Nick Piggin
2007-06-24  1:45 ` Nick Piggin
2007-06-24  1:46 ` [patch 1/3] add the fsblock layer Nick Piggin
2007-06-24  1:46   ` Nick Piggin
2007-06-24 15:28   ` Andi Kleen
2007-06-24 15:28     ` Andi Kleen
2007-06-24 20:18     ` Arjan van de Ven
2007-06-24 20:18       ` Arjan van de Ven
2007-06-25  8:58       ` Andi Kleen
2007-06-25  8:58         ` Andi Kleen
2007-06-25  7:19     ` Nick Piggin [this message]
2007-06-25  7:19       ` Nick Piggin
2007-06-24 23:01   ` Neil Brown
2007-06-24 23:01     ` Neil Brown
2007-06-25  7:41     ` Nick Piggin
2007-06-25  7:41       ` Nick Piggin
2007-06-25 12:29       ` Chris Mason
2007-06-25 12:29         ` Chris Mason
2007-06-26  2:34         ` Nick Piggin
2007-06-26  2:34           ` Nick Piggin
2007-06-26  2:48           ` Neil Brown
2007-06-26  2:48             ` Neil Brown
2007-06-26  3:07             ` Nick Piggin
2007-06-26  3:07               ` Nick Piggin
2007-06-26 12:26               ` Chris Mason
2007-06-26 12:26                 ` Chris Mason
2007-06-30 10:40                 ` Christoph Hellwig
2007-06-30 10:40                   ` Christoph Hellwig
2007-06-30 10:40           ` Christoph Hellwig
2007-06-30 10:40             ` Christoph Hellwig
2007-06-25 13:19   ` Chris Mason
2007-06-25 13:19     ` Chris Mason
2007-06-26  2:42     ` Nick Piggin
2007-06-26  2:42       ` Nick Piggin
2007-06-24  1:46 ` [patch 2/3] block_dev: convert to fsblock Nick Piggin
2007-06-24  1:46   ` Nick Piggin
2007-06-24  1:47 ` [patch 3/3] minix: " Nick Piggin
2007-06-24  1:47   ` Nick Piggin
2007-06-24  1:53 ` [RFC] fsblock Nick Piggin
2007-06-24  1:53   ` Nick Piggin
2007-06-24  3:07 ` Jeff Garzik
2007-06-24  3:07   ` Jeff Garzik
2007-06-24  3:47   ` Nick Piggin
2007-06-24  3:47     ` Nick Piggin
2007-06-24 13:51     ` Chris Mason
2007-06-24 13:51       ` Chris Mason
2007-06-25  6:58       ` Nick Piggin
2007-06-25  6:58         ` Nick Piggin
2007-06-25 12:25         ` Chris Mason
2007-06-25 12:25           ` Chris Mason
2007-06-30 10:44           ` Christoph Hellwig
2007-06-30 10:44             ` Christoph Hellwig
2007-06-30 10:42   ` Christoph Hellwig
2007-06-30 10:42     ` Christoph Hellwig
2007-06-30 11:10     ` Jeff Garzik
2007-06-30 11:10       ` Jeff Garzik
2007-06-30 11:13       ` Christoph Hellwig
2007-06-30 11:13         ` Christoph Hellwig
2007-06-24  4:19 ` William Lee Irwin III
2007-06-24  4:19   ` William Lee Irwin III
2007-06-24 14:16 ` Andi Kleen
2007-06-24 14:16   ` Andi Kleen
2007-06-25  7:16   ` Nick Piggin
2007-06-25  7:16     ` Nick Piggin
2007-06-26  3:06 ` David Chinner
2007-06-26  3:06   ` David Chinner
2007-06-26  3:55   ` Nick Piggin
2007-06-26  3:55     ` Nick Piggin
2007-06-26  9:23     ` David Chinner
2007-06-26  9:23       ` David Chinner
2007-06-26 11:14       ` Nick Piggin
2007-06-26 11:14         ` Nick Piggin
2007-06-27 12:39         ` Kyle Moffett
2007-06-27 12:39           ` Kyle Moffett
2007-06-26 12:34       ` Chris Mason
2007-06-26 12:34         ` Chris Mason
2007-06-27  5:32         ` Nick Piggin
2007-06-27  5:32           ` Nick Piggin
2007-06-27  6:05           ` David Chinner
2007-06-27  6:05             ` David Chinner
2007-06-27 11:50           ` Chris Mason
2007-06-27 11:50             ` Chris Mason
2007-06-27 15:18             ` Anton Altaparmakov
2007-06-27 15:18               ` Anton Altaparmakov
2007-06-27 22:35             ` David Chinner
2007-06-27 22:35               ` David Chinner
2007-06-28  2:44               ` Nick Piggin
2007-06-28  2:44                 ` Nick Piggin
2007-06-28 12:20                 ` Chris Mason
2007-06-28 12:20                   ` Chris Mason
2007-06-29  2:08                   ` David Chinner
2007-06-29  2:08                     ` David Chinner
2007-06-29  2:33                   ` Nick Piggin
2007-06-29  2:33                     ` Nick Piggin
2007-06-30 11:05 ` Christoph Hellwig
2007-06-30 11:05   ` Christoph Hellwig
2007-07-09 17:14 ` Christoph Lameter
2007-07-09 17:14   ` Christoph Lameter
2007-07-10  0:54   ` Nick Piggin
2007-07-10  0:54     ` Nick Piggin
2007-07-10  0:59     ` Christoph Lameter
2007-07-10  0:59       ` Christoph Lameter
2007-07-10  1:07       ` Nick Piggin
2007-07-10  1:07         ` Nick Piggin
2007-07-10  1:37       ` Dave McCracken
2007-07-10  1:37         ` Dave McCracken

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=467F6C8F.9040400@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=andi@firstfloor.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.