From: Andi Kleen <ak@suse.de>
To: Adam Heath <doogie@debian.org>
Cc: Andi Kleen <ak@suse.de>,
"Martin K. Petersen" <mkp@wildopensource.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
akpm@osdl.org, tony.luck@intel.com
Subject: Re: [PATCH] General purpose zeroed page slab
Date: Fri, 15 Oct 2004 01:18:38 +0000 [thread overview]
Message-ID: <20041015011838.GC9753@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0410141836270.1221@gradall.private.brainfood.com>
On Thu, Oct 14, 2004 at 06:36:47PM -0500, Adam Heath wrote:
> On Thu, 14 Oct 2004, Andi Kleen wrote:
>
> > Also that's pretty dumb. How about keeping track how much of the
> > page got non zeroed (e.g. by using a few free words in struct page
> > for a coarse grained dirty bitmap)
> >
> > Then you could memset on free only the parts that got actually
> > changed, and never waste cache lines for anything else.
>
> That will fail when a struct is placed in the page, and only the beginning and
> end of the struct was changed.
Hmm? I think you're misunderstanding me. The dirty bitmap would cover
all areas that are potentially not zero. If someone changes a byte
without setting the bitmap they're buggy.
-Andi
>
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Adam Heath <doogie@debian.org>
Cc: Andi Kleen <ak@suse.de>,
"Martin K. Petersen" <mkp@wildopensource.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
akpm@osdl.org, tony.luck@intel.com
Subject: Re: [PATCH] General purpose zeroed page slab
Date: Fri, 15 Oct 2004 03:18:38 +0200 [thread overview]
Message-ID: <20041015011838.GC9753@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0410141836270.1221@gradall.private.brainfood.com>
On Thu, Oct 14, 2004 at 06:36:47PM -0500, Adam Heath wrote:
> On Thu, 14 Oct 2004, Andi Kleen wrote:
>
> > Also that's pretty dumb. How about keeping track how much of the
> > page got non zeroed (e.g. by using a few free words in struct page
> > for a coarse grained dirty bitmap)
> >
> > Then you could memset on free only the parts that got actually
> > changed, and never waste cache lines for anything else.
>
> That will fail when a struct is placed in the page, and only the beginning and
> end of the struct was changed.
Hmm? I think you're misunderstanding me. The dirty bitmap would cover
all areas that are potentially not zero. If someone changes a byte
without setting the bitmap they're buggy.
-Andi
>
next prev parent reply other threads:[~2004-10-15 1:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 16:50 [PATCH] General purpose zeroed page slab Martin K. Petersen
2004-10-14 16:50 ` Martin K. Petersen
2004-10-14 17:30 ` Brian Gerst
2004-10-14 17:30 ` Brian Gerst
2004-10-14 17:36 ` Matthew Wilcox
2004-10-14 17:36 ` Matthew Wilcox
2004-10-14 18:49 ` Dave Jones
2004-10-14 18:49 ` Dave Jones
2004-10-14 19:08 ` Denis Vlasenko
2004-10-14 19:08 ` Denis Vlasenko
2004-10-14 19:47 ` Matthew Wilcox
2004-10-14 19:47 ` Matthew Wilcox
2004-10-14 18:04 ` Andi Kleen
2004-10-14 18:04 ` Andi Kleen
2004-10-14 23:36 ` Adam Heath
2004-10-14 23:36 ` Adam Heath
2004-10-15 1:18 ` Andi Kleen [this message]
2004-10-15 1:18 ` Andi Kleen
2004-10-18 18:06 ` Martin K. Petersen
2004-10-18 18:06 ` Martin K. Petersen
2004-10-18 18:42 ` Matthew Wilcox
2004-10-18 18:42 ` Matthew Wilcox
2004-10-18 18:54 ` Martin K. Petersen
2004-10-18 18:54 ` Martin K. Petersen
2004-10-18 19:06 ` Andi Kleen
2004-10-18 19:06 ` Andi Kleen
2004-10-18 21:06 ` Andi Kleen
2004-10-18 21:06 ` Andi Kleen
2004-10-18 19:03 ` Luck, Tony
2004-10-18 19:03 ` Luck, Tony
2004-10-18 19:14 ` Matthew Wilcox
2004-10-18 19:14 ` Matthew Wilcox
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=20041015011838.GC9753@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=doogie@debian.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkp@wildopensource.com \
--cc=tony.luck@intel.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 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.