> "Howell, David P" wrote:
> >
> > We are working on a proposal for redundant dump device support that I
plan
> > to
> > share in the next few weeks; I've got a prototype mostly working that
can be
> >
> > contributed. Let me know how you are approaching this, I'll send details
of
> > what we are doing here later this week. Sounds like a good opportunity
for
> > collaboration on this.
> >
> > Regards,
> > Dave Howell
>
> I'm really curious as to the proposal. Sounds like a good idea, the
> real question becomes, do you want to chain multiple dump devices with
> multiple dump mechanisms?
>
> Here's where I'm going with this. I just finished the code to allow
> people to install their own dump compression mechanisms (right now, it'll
> be RLE, I have to check in the GZIP compression module, and people can
> put in whatever one they want). Do you want to take the next step and
> let people have chains of dump mechanisms based on the dump condition?
> I realize multiple dump devices is good, but what if you could plug in
> your own dump method with it? Then that dump method could query the
> available dump devices configured.
>
> So you'd have:
>
> dump methods (one standard, but plug-and-play)
> dump devices (requires at least one, multiples allowed, maybe
> access lists for methods?)
> dump compressions (configurable, usable by some methods)
Do you mean as follows, Matt?
"Dump methods" means how to use devices configured for dump device to
save memory dump, and each of them should be pluggable?
(single device as standard, concatenating devices as single dump device,
mirroring devices for redundancy ...)
Each "dump devices" should be independently configurable about type of
compression and dump method ?
--Masashige
> Would this be the eventual goal? That way, everything is tunable to
> their own liking. I figured I'd ask, since if you're going to add in
> multiple dump devices, and we've gone to multiple compression types,
> you might as well go all the way and add dump methods as well. I
> don't know what the rest of the group thinks, but this could be
> very useful.
>
> I'd definitely like to get some feedback ... this is all doable,
> as long as the dump compression code is in 'lcrash', and the pages
> are dumped in a way that we can find the location in memory, this
> can work pretty sweet for everyone here.
>
> --Matt
|