From: Robin Holt <holt@sgi.com>
To: Kay Sievers <kay.sievers@vrfy.org>,
Jack Steiner <steiner@sgi.com>, Russ Anderson <rja@sgi.com>
Cc: Robin Holt <holt@sgi.com>, Greg Kroah-Hartmann <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: question about link_mem_sections()
Date: Thu, 22 Dec 2011 03:30:04 -0600 [thread overview]
Message-ID: <20111222093004.GH2547@sgi.com> (raw)
In-Reply-To: <CAPXgP11EBq-b1n7GS4qwS=Kco8yKsy2cRXJ7=iWO=z_GeJN9og@mail.gmail.com>
On Thu, Dec 22, 2011 at 02:18:47AM +0100, Kay Sievers wrote:
> On Mon, Dec 12, 2011 at 14:49, Robin Holt <holt@sgi.com> wrote:
> > On Mon, Dec 12, 2011 at 02:11:28PM +0100, Kay Sievers wrote:
>
> > If you do decide to rework that logic, we can retest for the next couple
> > months. We do not normally have a 16TB test machine lying around (IIRC,
> > the memory in something like that costs a couple million dollars), but we
> > do fortunately have one right now until the latter part of next quarter.
>
> The rework of the sys_devices with the goal to finally removal of all
> sysdev stuff is in Greg's tree now:
> http://git.kernel.org/?p=linux/kernel/git/gregkh/driver-core.git;a=shortlog;h=refs/heads/driver-core-next
> It will be available in linux-next.
>
> The hinted search moved from the 'kobject' to the 'bus' as:
> dev = subsys_find_device_by_id(&memory_subsys, block_id, hintdev);
>
> Would be nice if you can eventually give it a try, on the big box, to
> make sure we didn't break anything.
If it is in linux-next, we may already have it.
Russ or Jack, IIRC, you had been doing some testing with linux-next
on the 16TB machine. Is that correct? If so, do you happen to have a
timed boot log that we could look at?
Thanks,
Robin
prev parent reply other threads:[~2011-12-22 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 12:35 question about link_mem_sections() Kay Sievers
2011-12-12 12:45 ` Robin Holt
2011-12-12 13:11 ` Kay Sievers
2011-12-12 13:49 ` Robin Holt
2011-12-22 1:18 ` Kay Sievers
2011-12-22 9:30 ` Robin Holt [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=20111222093004.GH2547@sgi.com \
--to=holt@sgi.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rja@sgi.com \
--cc=steiner@sgi.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;
as well as URLs for NNTP newsgroup(s).