Re: [Boost-users] Serialization cumulatively.

Subject: Re: [Boost-users] Serialization cumulatively.
From: Tony Camuso (tcamuso_at_[hidden])
Date: 2015-03-20 15:57:03

On 03/20/2015 03:22 PM, Robert Ramey wrote:
> tcamuso wrote
>> Interestingly, the text archiver was giving me linefeeds for a while.
>
> I always thought it worked that way.  But I don't remember.
>
>> Now they aren't there.
>
> which surprise me.
>
>>> Of course you could hire me by the hour if you like.
>> :) I don't have that kind of money.
>
> how much does it cost all your customers to run your program for hours?

My customers are my fellow engineers who will likely run it as
a cron job at night, with all their other cron jobs. However,
there are times when you need to refresh on the spot, and waiting
an hour is a hideous prospect. Of course, most of us are balancing
more than one thing at a time, so it's just another context switch
in the big scheme of things.

Basically, what this thing does is look for exported symbols in the
Linux kernel. It uses the sparse library to do this. We are looking
for deeply nested structures that could affect the kernel application
binary interface (KABI). If changes are made to those structures
that are not KABI-safe, then problems can emerge with 3rd party apps
that use the KABI.

The idea is to provide kernel developers with a tool that can
expose whether the data structure they are considering for change
could affect the KABI. We have means to protect such changes,
but it's difficult to know when to use them without a tool that
can plumb the depths looking for any and all dependencies an
exported symbol may have.

Many thanks and warm regards,
Tony Camuso
Platform Enablement
Red Hat