Re: [RFC] Addition of link-layer header types for PCI, PCI-X, and PCI-Express

[Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Guy Harris <gharris () sonic net>
>
> Date: Sat, 24 Oct 2020 23:05:14 -0700
>
> On Oct 21, 2020, at 1:56 PM, Aki Van Ness via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:
>
> > I'm working on a project that plans to store PCI and PCI-Express
> > packets in the pcapng format as that's the most appropriate storage
> > format and I really rather not roll something custom.
> >
> > As such what are thoughts on adding Link-Layer types for PCI, PCI-X,
> > and PCI-Express?
>
> It seems reasonable, given that we have USB, Infiniband, and the DisplayPort AUX channel.
>
> > And would you want to group all versions of PCI, PCI-X, and
> > PCI-Express together or have them be their own values?
>
> Would each version need its own LINKTYPE_ value, or would a single metadata header and payload suffice for all versions 
> of PCI, all versions of PCI-X, and all versions of PCIe?  From a quick look at the Wikipedia pages for those, for what 
> that's worth, they changes for each seem to be at the physical layer, with full or at least significant backwards 
> compatibility, so, other than additional bits of metadata, would LINKTYPE_PCI, LINKTYPE_PCI_X, and LINKTYPE_PCI_EXPRESS 
> suffice?
>
> I'm assuming that the metadata would be different between PCI, PCI-X, and PCIe.
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers