Draft 4.

...

4 (2011 October 19)

Note that in the repository both rce and release appear at the top level.

Universal constants (constants.hh)

All RCEs whether of Gen I or Gen II each have the same limits on the number of plugin instances (MAX_PLUGINS).

Port-type enumeration (PortTypes.hh)

The numbers are members of an enumeration assigned by the DAQ project.

The header file also contains a specialization of the template RCE::service::EnumInfo which allows one to use the function templates emin<>(), emax<>(), ecount<>(), evalid<>(), enext<>(), eprev<>() and estr<>():

namespacestatic RCEconst {

 unsigned MAX_PLUGINS  = namespace ppi {

        static const unsigned MAX_PLUGINS  =  8;8;

enum PortType {
    CONFIG_FLASH,
    ETHERNET,
    PGP,
    class Port;etc.,
        class PortList;
        enum  PortType;
        class VirtualChannel;
    }
}

release/
    rce/
        ppi/
            constants.hh
            Port.hh
            PortList.hh
            PortType.hh
            VirtualChannel.hh

static const unsigned MAX_PLUGINS  =  8;

enum PortType {
    CONFIG_FLASH,
    ETHERNET,
    PGP1,
    PGP2,
    etc.,
    INVALID_PORTTYPE
};

emin<PortType>() == CONFIG_FLASH
emax<PortType>() == PortType(INVALID_PORTTYPE - 1)
ecount<PortType>() == int(INVALID_PORTTYPE)
evalid(x) is true for all from emin() to emax() inclusive, else false
enext(emax()) == eprev(emin()) == INVALID_PORTTYPE
enext(CONFIG_FLASH) == ETHERNET, etc.
eprev(ETHERNET) == CONFIG_FLASH, etc.
estr(CONFIG_FLASH) == "CONFIG_FLASH", etc.
estr(x) == "**INVALID**" if and only if evalid(x) is false

INVALID_PORT_TYPE
};

The header file also contains a specialization of the template tool::type::EnumInfo which allows one to use the function templates emin<>(), emax<>(), ecount<>(), evalid<>(), enext<>(), eprev<>() and estr<>():

emin<PortType>() == CONFIG_FLASH
emax<PortType>() == PortType(INVALID_PORTTYPE - 1)
ecount<PortType>() == int(INVALID_PORTTYPE)
evalid(PortType x) is true for all from emin() to emax() inclusive, else false
evalid(int) and evalid(unsigned) make similar tests on ints and unsigneds.
enext(emax()) == eprev(emin()) == INVALID_PORTTYPE
enext(CONFIG_FLASH) == ETHERNET, etc.
eprev(ETHERNET) == CONFIG_FLASH, etc.
estr(CONFIG_FLASH) == "CONFIG_FLASH", etc.
estr(x) == "**INVALID**" if and only if evalid(x) is false

ecount<>() can't be used as a dimension for static arrays since the compiler considers it to be non-constant; in that case use EnumInfo<PortType>::count.

Port list (PortList.hh)

This class is a Borg-type singleton; the constructor makes a stateless object whose member functions access the true (shared) state defined elsewhere. The shared state is constructed at system startup. The destructor destroys these stateless objects but does not touch the true state information. You can therefore just use the constructor whenever you need to access the One True List, e.g., PortList().head().

You can get a count of the number of ports or the first port on the list (the list can't be empty). The report() member function will print informational messages in the system log which show the contents of the port list in brief form, one line per port.

A particular port may be looked up in several different ways:

• By its global index number, assigned in sequence starting from zero as ports are created.
• By its type number and the index number within the type. The first ethernet port would be (ETHERNET,0), the second (ETHERNET,1), etc.
• By the number of the conduit the port is connected to.

Lookup methods return the null pointer if the search fails.

class PortList {
public:
    PortList() {}
    ~PortList() {}
    int numPorts() const;
    Port* head() const;
    Port* lookup(PortType type, unsigned typeIndex) const;
    Port* lookup(unsigned index) const;
    Port* lookupByConduit(unsigned conduit) const;
    void report() const;
);

Port (Port.hh)

A port object represents a particular instance of a protocol plug-in. Each port object is created at system startup. Port objects live until system shutdown and may not be copied or assigned.

Each port allocates and deallocates VirtualChannel objects on demand. During its lifetime each VirtualChannel object has exclusive use of one of the port's virtual channel numbers; the virtual channel number becomes available again once the VirtualChannel object is deallocated. The application code may request a specific, unused virtual channel number for the type of port, e.g., a well-known TCP port number. The application may also allow the port to assign a number not currently in use by any VirtualChannel.

Every port object is a member of the linked list accessed though class PortList and may not be removed from the list. Use the next() member function to iterate over the list.

A short name for the type and a short description of the port are also provided.

A "lost" counter is provided which counts the number of inbound messages that were discarded, for whatever reason.

Other information provided:

• The index number of the conduit associated with the port.
• The hardware version number of the associated plugin.
• The software version number of the associated plugin module.
• A bitmask giving the FPGA pins (if any) used by the plugin.
• The size of the VC-number space.

The report() member function produces detailed multi-line description of the port in the system log, including all platform-specific information.

High-level and mid-level code isn't allowed to create or destroy instances; only low-level code is allowed to do that

ecount<>() can't be used as a dimension for static arrays since the compiler considers it to be non-constant; in that case use EnumInfo<PortType>::count.

Port list (PortList.hh)

This class is a Borg-type singleton; the constructor makes a stateless object whose member functions access the true (shared) state defined elsewhere. The destructor destroys these stateless objects but does not touch the true state information. You can therefore just use the constructor whenever you need to access the One True List, e.g., PortList().head().

You can get a count of the number of ports or the first port on the list (the list can't be empty). The report() member function will print informational messages in the system log which show the contents of the port list in brief form, one line per port.

A particular port may be looked up in several different ways:

• By its global index number, assigned in sequence starting from zero as ports are created.
• By its type number and the index number within the type, e.g., (ETHERNET,0), (ETHERNET,1), etc.
• By the number of the conduit the port is connected to.

Lookup methods return the null pointer if the search fails.

class PortListPort {
public:
    PortList() {}
VirtualChannel* allocate(int vcNum);
    VirtualChannel* ~PortListallocate() {};
    intvoid numChannelsdeallocate(VirtualChannel *) const;
    Port*unsigned headlost() const;
    Port*unsigned lookup(PortType type,index() const;
    unsigned typeSeqtype() const;
    Portconst char* lookup(name() const;
    unsigned indextypeIndex() const;
    Port*uunsigned lookupByConduitconduit(unsigned conduit) const;
    voidunsigned reportversionHard() const;
    unsigned versionSoft() const;

    Port* next() const;
    const char* description() const;
    unsigned maxVcs() const;
    void report() const;
};

Virtual channel (VirtualChannel

.hh)

A port object represents a particular instance of a protocol plug-in. Each port object is created at system startup. Port objects live until system shutdown and may not be copied or assigned.

Each port creates and destroys VirtualChannel objects on demand. During its lifetime each VirtualChannel object has exclusive use of one of the port's virtual channel numbers; the virtual channel number becomes available again once the VirtualChannel object is deallocated. The client code may request a specific, unused virtual channel number for the type of port, e.g., a well-known TCP port number. The client may also allow the port to assign a number not currently in use by any VirtualChannel.

Every port object is a member of the linked list accessed though class PortList and may not be removed from the list. Use the next() member function to iterate over the list.

A short name for the type and a short description of the port are also provided.

A "lost" counter is provided which counts the number of incoming frames that were discarded, for whatever reason, instead of being queued in a virtual channel.

Other information provided:

• The index number of the conduit associated with the port.
• The hardware version number of the associated plugin.
• The software version number of the associated plugin module.

The report() member function produces detailed multi-line description of the port in the system log, including all platform-specific information.

Each VirtualChannel object is allocated by a Port and is assigned a unique ID in the Port's virtual channel number space.

Messages inbound on the associated port may be waited for and retrieved using the receive() member function, which returns a void* pointer to the payload portion of a message. Client code will normally keep a payload for a short time then give it back to the virtual channel they got it from using the virtual channel's deallocate() member function. It's an error to request a virtual channel to deallocate a payload it didn't produce; the result of doing so will be unpredictable.

A virtual channel takes message payloads given to its transmit() member function via void* pointers and queues them for output. The payload pointer must have been produced by the allocate() member function of the same virtual channel (or its receive()); breaking this rule results in unpredictable behavior. Once the message is transmitted the message buffer is automatically deallocated, so the user should not try to use it after calling transmit(). When allocating a buffer the client must specify the maximum size of the payload to be transmitted (in Gen I systems this is ignored since all buffers for a port will be the same size)Application code isn't allowed to create or destroy instances; only the RCE boot code is allowed to do that.

class PortVirtualChannel {
public:
    VirtualChannel*unsigned allocatevcNum(int) portNum)const;

    VirtualChannelvoid* allocatereceive();
    void deallocate(VirtualChannel *);
    unsigned lost() const;// To receive: first call this ...
    unsignedvoid indexdeallocate(void*) const;
   // unsigned type() const;... then this.

    const charvoid* nameallocate(size_t payloadSize) const;
    unsigned typeIndex() const;; // To transmit: first call this (or receive()) ...
    unsignedvoid conduittransmit(void*); const;
    unsigned versionHard() const;
    unsigned versionSoft() const;
  // ... Port* next() const;
    const char* description() const;
    void report() const;
then this.
};

Virtual channel (VirtualChannel.hh)

Each VirtualChannel object is created by a port and is assigned a unique ID in the port's virtual channel number space.

Incoming frames on the associated port may be waited for and retrieved using the wait() member function. Client code will normally keep a frame for a short time then give it back to the virtual channel they got it from using the virtual channel's giveBack() member function. It's an error to try to give back a frame to a virtual channel which didn't produce it; the results of doing so will be unpredictable.

A virtual channel takes frames given to its send() member function and queues them for output. The frame buffer is NOT reclaimed after sending nor does the plugin interface tell you when it's safe to re-use the buffer; that's up to the message protocol.

class VirtualChannel {
public:
    unsigned index() const;
    void* wait();
    void giveBack(void *frame);
    void send(void *frame);
};

Low level API

In this section we describe the code used to manage configuration information and construct the global PortList. Some of the classes already introduced above will have new members described here; other classes will be completely new.

New members of old classes

The PortList class has a static member function build() whose main purpose is to produce the list of Port instances. To do so it will have to read configuration information about plugins and conduits, load and activate plugin software and match conduits to ports. There is also a member function add() which places a new Port on the end of the list.

class PortList {
  public:
  static void build();
  private:
  void add(Port*);
};

The Port class' constructor is used by PortList::build(). It's constructor and destructor are used by derived classes. Also provided are the means to increment the count of lost messages, to set the next-port member and to find out the set of FPGA pins used by the port.

C++ interface for RCE boot code

In this section we describe the code used manage configuration information and construct the global PortList. Some of the classes already introduced above will have new members described here; other classes will be completely new.

New members of old classes

The PortList class has a static member function build() whose main purpose is to produce the list of Port instances. To do so it will have to read configuration information about plugins and conduits, load and activate plugin software and match conduits to ports.

class PortListPort {
protected:
   public:
Port(unsigned index,
    static  void build(); 
};

Boot code classes and their responsibilities

Namespaces and header files

The boot code classes described here are considered private to the package so they appear in the src/ directory under ppi/. However, they use the same namespace RCE::ppi as the application classes.

ConduitConfig (ConduitConfig.hh)

This is a Plain Old Data (POD) class describing a single conduit. The default constructor sets all members to zero.

PortType type,
       const char *name,
       unsigned typeIndex,
       unsigned conduit,
       unsigned versionHard,
       unsigned versionSoft,
       const char* description,
       unsigned long long pins,
       unsigned maxVcs);
   virtual ~Port() = 0;
   unsigned long long pins() const;
   void incLost();
   void next(Port*);
};

Instances of VirtualChannel are created and destroyed only inside Ports. There is an access member added which gives the owning Port instance.

class VirtualChannel {
private:
  VirtualChannel(Port*, unsigned vcNum);
  ~VirtualChannel();
  Port* port() const;
};

New classes and their responsibilities

ConduitConfig (ConduitConfig.hh)

This class describes a single conduit.

The index value is set to 0xffffffff by ConfigReader to indicate a nonexistent conduit.default constructor creates an invalid instance, one that represents a conduit that doesn't exist. A member function tests whether the instance is a valid one.

structclass ConduitConfig {
 public:
 const unsigned index;
  const ConduitType type;
  const unsigned version;
  const unsigned long long pins;
  ConduitConfig();
  ConduitConfig(unsigned ind, ConduitType, unsigned ver, unsigned long long);
  bool isValid() const;
};

ConduitType (ConduitType.hh)

These types are not well defined yet so for now we just define a generic type code. The header also provides a specialization of rcetool::servicetype::EnumInfo<> similar to that provided for PluginTypePortType.

enum ConduitType {
  CONDUIT,
  INVALID_CONDUIT_TYPE
};

ConfigReader (ConfigReader.hh)

One member function returns instances of PluginConfig, the other returns instances of ConduitConfig. Both take an argument that is the index of the object whose configuration you want to look up; plugins and conduits are numbered separately staring starting from zero. Both set the index to 0xffffffff when ther's no object associated with the given indexThe lookups return invalid config instances if the requested entities don't exist.

Instances have no data of their own but get what they need from ConfigSpace; you can generate and throw away instances as often as you want.

class ConfigReader {
  public:
  void lookupConduit(unsigned index, ConduitConfig&) const;
  void lookupPlugin(unsigned index, PluginConfig&) const;
};

ConfigSpace (ConfigSpace.hh)

Each instance implements an abstract space of configuration registers. How the abstract registers are used to collect configuration information is an implementation decision which will however be the same for both Gen I and II. Register addresses start at zero; an attempt to read or write a register at an invalid address, or to write to a read-only register, will throw std::logic_error. Use the implements() member function to determine if a virtual register is implemented at a given address.

Instances have Instances have no data of their own but get what they need from some central source on the RCE; exactly where differs between Gen I and Gen II. You can create and destroy instances at will.

class ConfigSpace {
  public:
  ConfigSpace();
  bool implements(unsigned address) const;
  unsigned read(unsigned address) const;
  void write(unsigned address, unsigned value);
};

PluginConfig (PluginConfig.hh)

This is a Plain Old Data (POD) class describing class describes a single plugin instance. The default constructor sets all members to zero.

The index value is set to 0xffffffff by ConfigReader to indicate a nonexistent plugin.default constructor creates an invalid instance, one that represents a plugin that doesn't exist. A member function tests whether the instance is a valid one.

struct PluginConfig {
  const unsigned index;
  const PluginTypePortType type;
  const unsigned version;
  const unsigned long long pins;
  PluginConfig();
  PluginConfig(unsigned ind, PluginTypePortType, unsigned ver, unsigned long long);
  bool isValid() const;
};

PortFactory (PortFactory.hh)

This is an abstract base class. Once the boot system startup code knows the types of the available plugins it will load the plugin software module for each type. It will call the entry point of each plugin software module once to obtain an instance of a class derived from PortFactory.

Once it has matched a PluginConfig instance with a ConduitConfig instance, or determines that the plugin needs no conduit, the boot startup code uses the factory object to create Port instances for the given type of plugin. If the plugin and conduit versions are incompatible the factory member function will throw std::logic_error. It will do the same if no ConduitConfig is supplied when one is required.

The report function will log full details of the factory, including any platform-dependent information.

class PortFactory {
public:
  PortType type() const;
  const char* name() const;
  unsigned version() const;
  const char* description() const;
  Port* makePort(const PluginConfig&);
  Port* makePort(const PluginConfig&, const ConduitConfig&);
  PortFactory* next() const;
  void next(PortFactory*);
  void report() const = 0;
protected:
  PortFactory(PortType, const char* name, unsigned version, const char* description);
  ~PortFactory();
};

PortFactoryList (PortFactoryList.hh)

Another Borg singleton, very similar in concenpt concept to PortList; the underlying . This list of factories is built at about the same time as the list of ports. There is at most one factory per port type. The lookup function returns a null pointer if no matching factory is on the list. The report function logs a one-line summary per factory. New PortFactory instances are added to the end of the list.

class PortFactoryList {
public:
  PortFactoryList();
  PortFactory* head() const;
  unsigned numFactories() const;
  PortFactory* lookup(PortType) const;
  void report() const;
}  void add(PortFactory*);
};

Plugin software module interface PluginModule.hh

Each module's entry point is named rce_appmain; this symbol is recognized by the module build building system which places its value in the transfer address slot of the module's ELF header. The prototype of the entry point function is

extern "C" PortFactory* rce_appmain();

The boot system startup code uses placement new to construct an instance of PluginModule atop the image of the module then calls the run() member function class PluginModule to find existing plugin modules and run them, or to save plugin software modules in the usual place given their images in memory. The first constructor fetches the module from some internal RCE storage while the second one reads it from a file. In either case one may then write the module to internal storage or run it to obtain the factory object. Once the module has been run any attempt to write it will throw std::logic_error because the module code will no longer be relocatable.

class PluginModule: public RCE::ELF::Module {
public:
  typedef FactoryPortFactory* (*EntryPoint)();
  Factoryexplicit PluginModule(PortType);
  PluginModule(PortType, const char* filename);
  PortFactory* run();
  void write() const;
};

The module's entry point is run directly without creating a new thread (otherwise we'd need synchronization in order to wait for the factory to be produced).

Gen I-specific

initialization

On Gen I RCEs the application software is left with the job of allocating I/O buffers and it can't do that without knowing for each plugin the header sizes, max payload sizes and max number of frame message buffers for import and export. That information is available from the port factories but it means downcasting the PortFactory* values gotten from the PortFactoryList. Not only must TDEs for the inbound buffers be allocated but administrative information must be placed in them (instances of class Buffer, see below). Import buffers must be pushed into an FLB pushed into one or more FLBs before any data may be received. The interface described here lets the application do the needed initialization without exposing the innards of the plugin-handling system.

Ethernet (TBD)

PGP

PgpBuffers

PgpSetup (

PgpSetup.hh)

An Creating an instance of this class provides performs the following :

• The offset from the beginning of the frame buffer to the header.
• The size of the header.
• The maximum payload size of a payload.
• The maximum number of import and export buffers that may be allocated.
• A means to allocate a pool of import buffers that have the required administration information added and which are given to the FLB that all the PGP1 plugins share.
• A means to allocate an export buffer pool with the required admin. info. in each buffer.
• A means to extract the allocated export buffers which returns a null pointer when all have been extracted.

class PgpBuffers {
public:
  PgpBuffers();
  ~PgpBuffers();

  class Allocator {
  public:
    virtual void* allocate(unsigned nbytes) = 0;
    virtual void  deallocate(void*) = 0;
  };

  unsigned headerOffset() const;
  unsigned headerSize() const;
  unsigned payloadOffset() const;
  unsigned maxPayloadSize() const;
  unsigned maxImportBuffers() const;
  unsigned maxExportBuffers() const;
  void allocateImportBuffers(unsigned numImport);
  void allocateExportBuffers(unsigned numExport);
  void allocateImportBuffers(unsigned numImport, Allocator &);
  void allocateExportBuffers(unsigned numExport, Allocator &);
  void* getExportBuffer();
};

functions:

• Allocates I/O buffers.
• Write TDEs to the FLB FIFO.
• Brings up the MGT links for the requested ports.
• Resets the appropriate PIC blocks and enables their events.

If you request a PGP port that does not exist then the constructor will throw std::logic_error. If any other initialization fails the constructor will throw std::runtime_error.

Early versions will used cached memory for I/O buffers as has been done in the past. Later versions will used uncached memory. Buffers for inbound messages are shared amongst all PGP ports while each port has its own pool of buffers for outbound messages. The default is to to use all PGP ports and to allocate the maximum number of each kind of buffer with the maximum payload size allowed for the PGP ports. If you request more buffers than the maximum then the maximum number is allocated.

The destructor deallocates all the buffers allocated by the constructor and resets the selected PIC blocks again, this time disabling their events.

Though header sizes and max payload sizes for inbound and outbound messages differ slightly, this class will allocate the maximum for each buffer. Inbound and outbound buffers will differ only in how the length parameter is set in the transaction descriptor since its interpretation varies depending on the direction of transfer.

class PgpSetup {
public:
  enum Port {PORT0=1, PORT1=2, PORT2=4, PORT3=8};
  enum {ALL=-1, DEFAULT=-1};

  explicit SetupPgp
  (int portMask                 =ALL,  // Either ALL or a logical OR of values from enum Port.
   int numInboundBuffers        =ALL,
   int numOutboundBuffersPerPort=ALL,
   int maxPayloadSize           =ALL,
   int resumeThreshold          =DEFAULT  // Either DEFAULT or the FLB resume threshold.
  );

  ~SetupPgp();

  int portMask()                  const;
  int numInboundBuffers()         const;
  int numOutboundBuffersPerPort() const;
  int headerSize()                const;
  int maxPayloadSize()            const;
  int resumeThreshold()           const;
};

Gen I-specific low-level API

Buffer (Buffer.hh)

On Gen I hardware each message is represented by a data structure in main memory called a Transaction Descriptor. The descriptor contains pointers to all the other message-related data:

• Message header
• Message payload
• Transaction completion descriptor.

The allocation and preparation of the descriptor and the other message data is the responsibility of software; the firmware doesn't manage them. For simplicity each message is represented in software by an instance of class Buffer. Each Buffer contains a Transaction Descriptor, Transaction Completion Descriptor, header buffer, payload buffer and next/previous Buffer pointers all welded together into a single object. Each part will have a fixed offset which is hard-coded into the object so that we don't have to refer to non-cached memory just to find out their addresses. For that reason we allocate a fixed number of bytes for the header no matter the type of plugin; the largest header is 32 bytes for the Petacache PGP non-register messages so we'll allocate twice that. The Transaction Descriptor has the strictest alignment requirement (see below) so it comes first. The payload is of variable size so it comes last.

The first word of a Transaction Descriptor is a length parameter whose interpretation depends on the direction of transfer. For outgoing messages it's the number of payload bytes to send. For incoming messages it's the maximum number of header+payload bytes that will be accepted. The plugin never alters the Transaction Descriptor so to see how many bytes were transferred one has to examine the transfer count in the Transaction Completion Descriptor. For reception the completion descriptor is always updated by the plugin while for transmission this happens only when the transaction fails.

A PIC block gives or takes a reference to a Transaction Descriptor in the form of a 32-bit value called a Transaction Descriptor Entry (TDE). Six of those bits are reserved for various flags, so a TDE contains only the upper 26 bits of the address of the descriptor. Perforce the descriptor must be allocated on a 64-byte boundary. The completion descriptor must be allocated on a PowerPC cache line boundary (32-byte boundary). Due to a design quirk PIC blocks write two complete cache lines when updating a completion descriptor, so the space allocated to each must be artificially enlarged.

For details about the descriptors see chapter 4 of the Cluster Element Module document at http://www.slac.stanford.edu/exp/npa/design/CEM.pdf

#include <rtems.h>

#define TRANSACTION_DESCRIPTOR_ALIGNMENT (64)
#define DMA_ALIGNMENT (PPC_CACHE_ALIGNMENT)

struct Buffer {

  enum {
    MAX_HEADER_SIZE  = 64,
    COMPLETION_DESCRIPTOR_SIZE  = 2 * PPC_CACHE_ALIGNMENT
  };

  struct Completion {
    unsigned parameter: 24;
    unsigned wasBlockError: 1;
    unsigned reason: 6;
    unsigned wasError: 1;
    uint32_t transferCount;
  };

  struct Transaction {
    uint32_t    lengthParameter;
    void*       const headerPtr;
    void*       const payloadPtr;
    volatile Completion* const completionPtr;
    Transaction(void* hPtr, void* pPtr, volatile Completion* cPtr);
  };


private:
  Transaction         m_transaction               __attribute__((aligned(TRANSACTION_DESCRIPTOR_ALIGNMENT)));
  Buffer*             m_next;
  Buffer*             m_prev;
  union {
    volatile Completion m_completion              __attribute__((aligned(DMA_ALIGNMENT)));
    uint8_t           m_pad0[COMPLETION_DESCRIPTOR_SIZE];
  } m_paddedComp;
  mutable uint8_t     m_header[MAX_HEADER_SIZE]   __attribute__((aligned(DMA_ALIGNMENT)));
  mutable uint8_t     m_payload;                  __attribute__((aligned(DMA_ALIGNMENT)));

public:
  static Buffer*      transactionToBuffer(Transaction*);
  static Transaction* bufferToTransaction(Buffer*);
  static Buffer*      tdrToBuffer(unsigned tdr);
  static unsigned     bufferToTdr(Buffer*);
  static Buffer*      payloadToBuffer(void*);

public:
  Buffer();
  Buffer*                    next()            const;
  Buffer*                    prev()            const;
  const volatile Completion* completion()      const;
  void*                      header()          const;
  void*                      payload()         const;
  void                       next(Buffer* p);
  void                       prev(Buffer* p);
  unsigned                   lengthParameter() const;
  void                       lengthParameter(unsigned);
};

Platform-specific information (PlatformInfo.hh and PlatformPluginInfo.hh)

The single PlatformInfo instance is basically an array of PlatformPluginInfo instances. The array holds information that has no place in the PortList instance and is searched in a similar manner. The factory classes for Gen I hardware will fill in the information inside their makePort() member functions. Later on such classes as PgpSetup will retrieve it.

The constructor returns a reference to the single instance. {addPlugin()}} adds a new plugin to the array, fills in the port type and index within type, returning a pointer to the new entry. The lookup() member functions behave much like their counterparts in class PortList.

class PlatformInfo {
public:
  PlatformInfo() {}
  const char*         platform    ()                                         const {return "ppc405-rtems";}
  PlatformPluginInfo* addPlugin   (ppi::basic::PortType, unsigned typeIndex);
  PlatformPluginInfo* lookupPlugin(ppi::basic::PortType, unsigned typeIndex);
  PlatformPluginInfo* lookupPlugin(unsigned index);
};

Each entry in the array is a simple struct containing the required information such as header sizes, payload sizes and PIC block assignments for the given port. The limit on import buffers is understood to apply to the FLB assigned to the port rather than the port itself. This is important when multiple ports share a common FLB as is done with PGP.

struct PlatformPluginInfo {
  basic::PortType type;
  unsigned index;
  unsigned typeIndex;
  unsigned importHeaderSize;
  unsigned maxImportPayloadSize;
  unsigned maxImportBuffers;
  unsigned exportHeaderSize;
  unsigned maxExportPayloadSize;
  unsigned maxExportBuffers;
  unsigned pibNum;
  unsigned pebNum;
  unsigned flbNum;
  unsigned ecbNum;
};

Ethernet (TBD)

PGP

Petacache

Port factory class (PetacachePgpFactory.hh)

An instance of this class is what the PGP plugin module will use to create instances of PgpPort. The first makePort() member function is non-functional and will throw std::runtime_error if called. The report() member function will log some messages describing the platform-dependent features of the PGP implementation.

In each buffer the administative information comes first followed by the header and then the payload. Header and payload sections are both aligned on a cache line boundary; the buffer itself is aligned on a 64-byte boundary. If the application doesn't provide its own allocator a default will be used.

The PgpBuffers object retains ownership of the buffers; the destructor resets all PGP firmware blocks and deallocates all the buffers. The application need only destroy the current instance and make a new one to restart PGP.

Gen I-specific plugin software interface

Buffer (Buffer.hh)

Before a frame buffer may be used for either import or export an instance of class Buffer must be created at the beginning of the buffer using placement new.

A Buffer contains regions of fixed size used in the management of the frame itself and its buffer:

• The firmware's in-memory descriptor. The firmware TDE for the frame points to the descriptor.
• Status. The firmware writes operation completion status here.
• One or more links used to make singly-linked lists.

Immediately following the end of the Buffer we have first the frame's header and then its payload.

The links, descriptor and status areas have the same sizes for all port types.

The descriptor must begin on a 64-byte boundary; for ease of layout the entire buffer also has that alignment. The header and payload areas should begin on cache-line boundaries (32-byte).
Buffer instances may not be copied or assigned.

Ethernet (TBD)

PGP version 1

Pgp1Factory

This class adds accessors to Gen-I specific information not found in the base class. The application interface class PgpBuffers will use it.

class Pgp1FactoryPetacachePgpFactory: public basic::PortFactory {
public:

   unsigned headerSizePetacachePgpFactory();

  virtual ~PetacachePgpFactory() const;

  virtual PgpPort* makePort(unsigned maxPayloadSize() const;
  unsigned maxImportBuffers() const;
  unsigned maxExportBuffers() const;
  unsigned pebBlock(unsigned index) const;
  unsigned ecbBlock() const;
  unsigned flbBlock() const;
  unsigned pibBlock(unsigned index) const; index, unsigned typeIndex, const basic::PluginConfig&);

  virtual PgpPort* makePort(
    unsigned index,
    unsigned typeIndex,
    const basic::PluginConfig& plugin,
    const basic::ConduitConfig& conduit);

  virtual void report() const;

};

Gen I PGP1 PGP plugins all share the same ECB and FLB but each is assigned its own PEB and PIB. The index you pass to the accessor function is the index within the plugin type PGP1PGP, the same number you would obtain from Port::typeIndex().

Gen I initialization of ConfigSpace

Configuration container zero in the configuration flash contains tables of information about the hardware and firmware; this information can't be gotten directly from the hardware and firmware.

Not knowing the actual layout of the RCE's circuit board(s) I've arbitrarily assigned conduit 0 to the 10 Gb ethernet and conduits 1, 2, 3 and (for petacache) 4 to PGP1plugin type PGP. The four MGT's assigned to the ethernet I call assign to pins 0-3 while the the ones assigned to the for PGP plugins I call assign to pins 4, 5, 6 and (peta) 7.

The container contents consist of eight instances of PluginConfig followed immediatly by eight instances of ConduitConfig, except that the "index" members are not recorded. For a Petacache RCE board (PGP only) the tables look like this: (substitute 0xffffffff for "EMPTY" and the enumerator values for "PGP1" and "CONDUIT" ):

Gen I storage of plugin software modules

Only a few different types of protocol plugins are found on Gen I systems so each type is assigned to a fixed Configuration container:

Later a container may be used for CONFIG_FLASH, if we ever manage to make a usable wrapper for the FCI package that makes it look like another plugin.

Use case: Gen I booting

1. Boot code:
   1. Loads and starts the system core.
2. System core
   1. Initializes the CPU.
   2. Initializes RTEMS.
   3. Initializes any extra C++ support.
   4. Sets up the MMU's TLB and enables the MMU.
   5. Creates the default instance of the dynamic linker.
   6. Reads ConfigSpace.
      1. The first read triggers the reading of Configuration container zero.
      2. Builds the Port and PortFactory lists, reading, linking and running plugin software modules as required.
   7. Performs other initialization, e.g., ethernet, BSD stack.
   8. Loads and links the application code using the default dynamic linker.
   9. Calls the application entry point.

Source code organization

All the classes, enums and other declarations will appear in the namespace RCE::ppi.

Platform-neutral header files for the application interface are immediately below the directory rce/ppi/.

Platform-neutral header files for the boot code and plugin software module interfaces are directly below rce/ppi/src/.

Platform-specific header files are in subdirectories gen1/, gen2/ and i86-linux/ below src/.

Platform-neutral compilation units are in src/ while those that depend on the platform are in src/gen1/, etc.

Inline definitions are broken out into their own header files in src/ or its subdirectories unless they are few and trivial for a given class. Example: Foo-inl.hh.

The EMPTY value must be one that is is not valid for conversion to either PortType or ConduitType; 0xffffffff will do. Replace "PGP" and "CONDUIT" with the numerical values of the corresponding enumerators.

Gen I storage of plugin software modules

Only a few different types of protocol plugins are found on Gen I systems so each type is assigned to a fixed Configuration container:

Later a container may be used for CONFIG_FLASH, if we ever manage to make a usable wrapper for the FCI package that makes it look like another plugin.

Use case: Gen I booting

1. Boot code:
   1. Loads and starts the system core.
2. System core
   1. Initializes the CPU.
   2. Initializes RTEMS.
   3. Initializes any extra C++ support.
   4. Sets up the MMU's TLB and enables the MMU.
   5. Creates the default instance of the dynamic linker.
   6. Reads ConfigSpace.
      1. The first read triggers the reading of Configuration container zero.
      2. Builds the Port and PortFactory lists, reading, linking and running plugin software modules as required.
   7. Performs other initialization, e.g., ethernet, BSD stack.
   8. Loads and links the application code using the default dynamic linker.
   9. Calls the application entry point.

Source code organization

All the classes, enums and other declarations will appear within the top-level namespace ppi and in namespaces nested within itUnit test code goes in rce/ppi/test/ whose subdirectory structure mirrors that of src/.