Re: debugging pseudo-file - viewing open file list from client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Was thinking about json a little more - looks like no kernel examples
(other than user space tools that produce, not consume from the
kernel) json (see e.g. "jsonw_printf")

More machine readable examples in debug output do exist - maybe format
more like an xfs example (see below), keep the output terse and then
we can let the proposed smbinfo (smb3info or whatever) dump this is
human readable form:

# cat /proc/fs/xfs/stat
extent_alloc 0 0 0 0
abt 0 0 0 0
blk_map 0 0 0 0 0 0 0
bmbt 0 0 0 0
dir 0 0 0 0

On Mon, Oct 22, 2018 at 3:51 AM Aurélien Aptel <aaptel@xxxxxxxx> wrote:
>
> I think we really should have a machine-readable file where we just dump
> everything in json or something and let a separate userspace tool filter
> and display things.
>
> There are a couple of consumers of the DebugData file (I know of at
> least PCP [1] but I'm sure there are others out there) and there's a
> high chance they break everytime we change the output.
>
> 1: https://pcp.io/
>    https://github.com/performancecopilot/pcp/tree/8c9b0442d0c5116d65f432e4c3aff0571f60efb8/src/pmdas/cifs
>
> --
> Aurélien Aptel / SUSE Labs Samba Team
> GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
> SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)



-- 
Thanks,

Steve




[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux