[lustre-devel] [PATCH 32/37] staging/lustre: use 64-bit times for exp_last_request_time
Drokin, Oleg
oleg.drokin at intel.com
Fri Sep 25 01:07:43 UTC 2015
On Sep 24, 2015, at 4:15 PM, Arnd Bergmann wrote:
>>>> Anyway this does remove a lot of stuff that we don't really need in the client,
>>>> I'll try to get it built and tested just to make sure it does not really break anything
>>>> (unfortunately it does not seem to apply cleanly to the tip of staging-next tree).
>>> Ok. I based the patches on top of my 37 patch series, and if you want I can
>>> upload a git branch somewhere to make rebasing easier.
>>
>> That would be great.
>> Though in the end likely this huge patch would need to be split into smaller chunks.
>> Like if all unused llog code removal is done, that would allow subsequent dt_object.[ch]
>> removal and so on.
>> But for testing a current snapshot would be great, then I can run it through my testbed
>> to see how it fares there.
>
> Ok, I've pushed out the branch to
>
> git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git y2038-lustre
>
> This contains the latest version of the y2038 series (with the warning fixed
> that Sudip Mukherjee found) but no other changes, and the big code removal
> on top.
These do seem to be working fine in my testing.
I also noticed we can remove some more stuff in at least fid/ dir so
I created some patches on top of your tree:
https://github.com/verygreen/linux/tree/fidcleanup
Also I've looked a bit into nm and I don't see a straight way of cross referencing
which globally visible functions are not really used by anything.
Do you have a handy recipe for that?
Thanks.
Bye,
Oleg
More information about the devel
mailing list