Re: [PATCH] x86, kdump: Set crashkernel_low automatically

[Vivek Goyal]

On Mon, Mar 11, 2013 at 01:57:41PM -0700, Yinghai Lu wrote:
> On Mon, Mar 11, 2013 at 1:45 PM, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote:
> > In my experience, trying to keep foot-print small has kind of been a
> > losing battle.
> >
> > - People want more functionality in second kernel, want to dump to more
> >   complicated IO stacks and that requires pulling in more drivers,
> >   more libraries, more daemons, more user space tools and what not.
> >
> > - Now we use dracut generated initramfs and it has been growing in size.
> >   Now systemd has been pulled in too.
> >
> > - Drivers keep on increasing their memory usage.
> 
> If the dump file will be only put one place, why should all the drivers
> for all devices get loaded?
> for example: dump will be on disk with one scsi controller, can you only
> load driver that contoller? and forget about all other storage controller and
> network etc drivers.

We do try to optimize things this way. Only include drivers as needed. But
a single driver might be handling lots of cards and then try to bring
up all the cards in second kernel.

Just fixed some issues with one driver where around 40MB extra memory
was benig consumed because of multiqueue support. Just bunch of allocation
in driver. And we used kernel command line to disable it.

Point being, in practice how many software development areas one can
change to keep memory requirement with-in few MBs. I have been doing
it for last few years and it has been very hard.

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/