From: Yasunori Goto <ygoto@fsw.fujitsu.com>
To: colpatch@us.ibm.com
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
akpm@us.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Remove memblks from the kernel
Date: Wed, 28 Jan 2004 14:08:13 -0800 [thread overview]
Message-ID: <20040128135302.2C5B.YGOTO@fsw.fujitsu.com> (raw)
In-Reply-To: <4016DE81.9080507@us.ibm.com>
Hello.
> Martin J. Bligh wrote:
> > This patch removes memblks from the kernel ... we don't use them, and
> > the NUMA API that was planning to use them when they were originally
> > designed isn't going to use them anymore. They're just unnecessary
> > added complexity now ... time for them to go.
> >
> > There's a slight complication in that ia64 uses something with a similar
> > name for part of its memory layout, but Jes Sorensen kindly untangled them
> > from each other for us. The patch with his modifications is below. Jes
> > tested it on ia64, and I testbuilt it with every config in my arsenal.
> >
> > Please apply ... thanks,
> >
> > M.
>
> As the unfortunate soul who pushed this whole memblk concept way back
> when, I'll add my support for their removal. The things I envisioned
> happening with memblks never materialized and so Martin is right, now
> they're just taking up space. Adios memblks, we barely knew ye.
OK.
I feel I have to agree removing memblk,
because my opinion is just concept and I don't have any patch yet.
If memblks will be needed again when we will be able to
support partial failure of memory, I will post the patch.
Good bye and Sayonara memblks.
I'm glad that some person heard my opinion.
Thanks.
--
Yasunori Goto <ygoto at fsw.fujitsu.com>
prev parent reply other threads:[~2004-01-28 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 7:35 Martin J. Bligh
2004-01-23 22:27 ` Yasunori Goto
2004-01-27 21:56 ` Matthew Dobson
2004-01-28 22:08 ` Yasunori Goto [this message]
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=20040128135302.2C5B.YGOTO@fsw.fujitsu.com \
--to=ygoto@fsw.fujitsu.com \
--cc=akpm@us.ibm.com \
--cc=colpatch@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome