frame 9e manual

frame 9e manual

Discover everything Scribd has to offer, including books and audiobooks from major publishers. Start Free Trial Cancel anytime. Report this Document Download Now Save Save Frame 9e Manual For Later 100% (2) 100% found this document useful (2 votes) 177 views 33 pages Frame 9e Manual Uploaded by Vikas Oza Description: Full description Save Save Frame 9e Manual For Later 100% 100% found this document useful, Mark this document as useful 0% 0% found this document not useful, Mark this document as not useful Embed Share Print Download Now Jump to Page You are on page 1 of 33 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language. Our advanced technology and service solutions deliver industry-leading value to your products. We know quality makes the difference. Run the numbers with our comparison tool. For a better experience, please enable JavaScript in your browser before proceeding. It may not display this or other websites correctly. You should upgrade or use an alternative browser. You (conspicuously) did not mention the type of combustion system (conventional, or DLN-I), or the types of fuels being burned by the unit(s). Both factors can play a big role in determining these operational limitations. Hope this helps. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.If you wish to opt out, please close your SlideShare account. Learn more. You can change your ad preferences anytime. Why not share! Ever since my years of high school, I really have no idea what professors are looking for to give good grades. After some google searching, I found this service ? www.WritePaper.info ? who helped me write my research paper. The final result was amazing, and I highly recommend ? www.WritePaper.info ?http://anmoul.com/userfiles/canon-fundus-camera-manual.xml

• ge gas turbine frame 9e manual, gt frame 9e manual, frame 9e gas turbine manual, frame 9e manual, frame 9e manual pdf, frame 9e manual transmission, frame 9e manual model, frame 9e manual user.

to anyone in the same mindset as me.Save so as not to loseAmong all the other tasks they get assigned in college, writing essays is one of the most difficult assignments. Fortunately for students, there are many offers nowadays which help to make this process easier. The best service which can help you is ? www.HelpWriting.net ?STAGE AFTER AND 3rd STAGE FORWARD ROTOR WHEELAND 2nd STAGE AFTER AND 3rd STAGE FORWARDNow customize the name of a clipboard to store your clips. Basic models produced by GE Energy cover the 5,000 to 124,000 kW power range. They can be provided in simple or regenerative cycles for mechanical drive or generator drive applications. The unit was developed in two configurations: a cold-end drive single shaft for power generation and a hot- end drive twin shaft for mechanical drive applications. Maximum commonality has been maintained between the single and twin shaft models. The design speed of the GE5-2 low pressure turbine is 12,500 rpm, with a capability range from 50% to 105%, which is ideal for direct coupling of GE Energy centrifugal compressors in the 6 MW power range. COMBUSTOR. The result is a standard package capable of satisfying the needs of a typical user for low installation and maintenance costs. This affords the GE5 a position of market leadership in cost and availability through innovative programs for service and sparing, and through package assembly and disassembly flexibility. It is the evolution of the field-proven PGT10A and incorporates the latest in aerodynamic design in a compact and versatile package arrangement. The design of the GE10 has been highly refined based on the extensive experience gained operating in all types of environments. The first-stage nozzles are cooled by the axial compressor discharge air. The MS5001 Gas Turbine is the ideal solution for power generation where low maintenance, reliability and economy of fuel utilization are required.http://www.crammotorsport.com/canon-fs36-manual.xml

Low operating and investment costs make the MS5001 package power plant an economically attractive system for load generation. The MS5002 gas turbine was introduced in the market in the 1970s and has been updated and up-rated over the years to meet the industry demand for increased output. Presently. The MS5002E will be available in both single and dual-shaft versions to cover power generation and mechanical drive applications. The high efficiency axial compressor has 17 stages. The combustor has ten combustion chambers with individual fuel nozzles. The machine has a three-stage impulse turbine. The power turbine of the PGT16 gas turbine is identical to that of the PGT10 heavy duty, high efficiency gas turbine which has been in operation for more than half a million hours. GAS GENERATOR The LM2500 GG has already accumulated several million fired hours not only as an aircraft engine (TF39 and CF6-6 engines), but also in the industrial field in many mechanical drive applications (marine, onshore and offshore gas transmission) and for generator drive service. Continuing the tradition of the established record of GE’s LM2500, the LM6000 is ideal as a source of drive-power for pipeline compression, offshore platform and gas re-injection, as well as for LNG compressors. Iron castings give dimensional and thermal stability to maintain good radial tip clearances for maximum power and efficiency.GE Energy Gas Turbines. In addition to variable stator vanes and blow-off valves, the design solutions include: - variable turbine nozzle guide vanes. This type of control philosophy applies principally to mechanical drive units, and consists of an exhaust temperature control curve that self adjusts according to the condition of the inlet filters and actual power turbine speed. The result is flawless performance of turbocompressors that have accumulated more than 100,000 hours of operation in the largest LNG plants in the world.

GE Energy turbocompressors are individually tailored to meet the customer’s performance requirements. We offer an extensive portfolio of proactive and interactive service products such as condition-based maintenance and long term service agreements complementing the traditional service offerings of OEM spare parts, repairs, and field services. This Training can be provided either at the client’s site or at the Learning Center located at GE Energy headquarters in Florence, Italy. Instructors are field-seasoned experts who combine their understanding of theory with practical experience. Wait for Forum instructions Start your sponsorship Would you like to sponsor the gas turbine end-user platform. Please contact us through Register page and choose the sponsor package best suited to your needs. The remainder of this manual introduces the aspects of writing devices drivers that leverage the MAC framework. While both the GLDv3 and MAC framework refer to the same thing, in this manual page we use the term the MAC framework to refer to the device driver interface. MAC device drivers are character devices. These callbacks control all the aspects of the device. They range from sending data, getting and setting of properties, controlling mac address filters, and also managing promiscuous mode. The MAC framework takes care of many aspects of the device driver's management. A device that uses the MAC framework does not have to worry about creating device nodes or implementing open(9E) or close(9E) routines. In addition, all of the work to interact with dlpi(7P) is taken care of automatically and transparently. Registering with MAC Every instance of a device should register separately with MAC. These steps should all be taken during a device's attach(9E) entry point. It is recommended that the driver perform this sequence of steps after the device has finished its initialization of the chipset and interrupts, though interrupts should not be enabled at that point.

In general, device drivers declare this statically. See the MAC Callbacks section for more information on how to fill it out. The handle that it uses to register with should be part of the driver's soft state. It will be used in various other support functions and callbacks. If the call is successful, then the device driver should enable interrupts and finish any other initialization required. MAC Callbacks The MAC framework interacts with a device driver through a series of callbacks. This section does not focus on the specific functions, but rather on interactions between them and the rest of the device driver framework. A device driver should make no assumptions about when the various callbacks will be called and whether or not they will be called simultaneously. As such, while some calls may be serialized to the device, such as setting properties, the device driver should always presume that all of its data needs to be protected with locks. Other routines in the DDI may be called while locks are held; however, device driver writers should be careful about calling blocking routines while locks are held or in interrupt context, though it is generally legal to do so. Receiving Data A device driver will often receive data through the means of an interrupt. When that interrupt occurs, the device driver will receive one or more frames with optional metadata. Often each frame has a corresponding descriptor which has information about whether or not there were errors or whether or not the device successfully checksummed the packet. In addition to the per-packet flow described below, there are certain requirements that drivers must adhere to when programming the hardware to receive data. See the section RECEIVE DESCRIPTOR LAYOUT for more information. During a single interrupt, a device driver should process a fixed number of frames. For each frame the device driver should: 1. First check whether or not the frame has errors.

If errors were detected, then the frame should not be sent to the operating system. If the device distinguishes between the types of errors, then separate kstats for each class of error are recommended. See the STATISTICS section for more information on the various error cases that should be considered. 2. Once the frame has been determined to be valid, the device driver should transform the frame into a mblk(9S). It is vitally important that all the frames be chained in the order that they were received. If the device driver mistakenly reorders frames, then it may cause performance impacts in the TCP stack and potentially impact application correctness. When this function is called, received data will be pushed through the networking stack and some replies may be generated and given to the driver to send out. It is not the device driver's responsibility to determine whether or not the system can keep up with a driver's delivery rate of frames. The rest of the networking stack will handle issues related to keeping up appropriately and ensure that kernel memory is not exhausted by packets that are not being processed. Finally, the device driver should make sure that any other housekeeping activities required for the ring are taken care of such that more data can be received. While the driver is processing the message blocks, it may run out of resources. For example, a transmit descriptor ring may become full. At that point, the device driver should return the remaining unprocessed frames. The act of returning frames indicates that the device has asserted flow control. Once this has been done, no additional calls will be made to the driver's transmit entry point and the back pressure will be propagated throughout the rest of the networking stack.

At some point in the future when resources have become available again, for example after an interrupt indicating that some portion of the transmit ring has been sent, then the device driver must notify the system that it can continue transmission. Interrupt Coalescing For devices operating at higher data rates, interrupt coalescing is an important part of a well functioning device and may impact the performance of the device. Not all devices support interrupt coalescing. If interrupt coalescing is supported on the device, it is recommended that device driver writers provide private properties for their device to control the interrupt coalescing rate. This will make it much easier to perform experiments and observe the impact of different interrupt rates on the rest of the system. MAC Address Filter Management The MAC framework will attempt to use as many MAC address filters as a device has. If the device driver runs out of filters, it should not take any special action and just return the appropriate error as documented in the corresponding manual pages for the entry points. The framework will ensure that the device is placed in promiscuous mode if it needs to. Link Updates It is the responsibility of the device driver to keep track of the data link's state. Many devices provide a means of receiving an interrupt when the state of the link changes. If the device driver does not properly inform the system about link changes, then various features like link aggregations and other mechanisms that leverage the link state will not work correctly. Link Speed and Auto-negotiation Many networking devices support more than one possible speed that they can operate at. The selection of a speed is often performed through auto-negotiation, though some devices allow the user to control what speeds are advertised and used. Logically, there are two different sets of things that the device driver needs to keep track of while it's operating: 1. The supported speeds in hardware. 2.

The enabled speeds from the user. By default, when a link first comes up, the device driver should generally configure the link to support the common set of speeds and perform auto- negotiation. For a full list of them, see the PROPERTIES section. See the Ethernet Link Properties section in dladm(1M) for more information. It's worth discussing how these different values get used throughout the different entry points. For a given speed, the driver should consult whether or not the hardware supports this speed. If it does, it should fill in the default value that the hardware takes and whether or not the property is writable. The properties should also be updated to indicate whether or not it is writable. Here, the device should first consult whether the given speed is supported. If it is not, then the driver should return ENOTSUP. If it does, then it should return the current value of the property. Here, the same logic applies. Before the driver considers whether or not the property is writable, it should first check whether or not it's a supported property. If it's not, then it should return ENOTSUP. Otherwise, it should proceed to check whether the property is writable, and if it is and a valid value, then it should update the property and restart the link's negotiation. Several of the statistics that are queried relate to auto-negotiation and hardware capabilities. The only thing that should be consulted is what the hardware itself supports. Otherwise, the statistics should look at what is currently being advertised by the device. Interacting with Devices Administrators always interact with devices through the dladm(1M) command line interface. The state of devices such as whether the link is considered up or down, various link properties such as the MTU, auto-negotiation state, and flow control state, are all exposed. It is also the preferred way that these properties are set and configured. While device tunables may be presented in a driver.

conf(4) file, it is recommended instead to expose such things through dladm(1M) private properties, whether explicitly documented or not. CAPABILITIES Capabilities in the MAC Framework are optional features that a device supports which indicate various hardware features that the device supports. The two current capabilities that the system supports are related to being able to hardware perform large send offloads (LSO), often also known as TCP segmentation and the ability for hardware to calculate and verify the checksums present in IPv4, IPV6, and protocol headers such as TCP and UDP. Each capability has its own constant and may have corresponding data that goes along with it and a specific structure that the device is required to fill in. Note, the set of capabilities changes over time and there are also private capabilities in the system. Several of the capabilities are used in the implementation of the MAC framework. It is important that the device driver handles unknown capabilities correctly. To indicate no support for any kind of checksumming, the driver should either set this value to zero or simply return that it doesn't support the capability. Note, the values that the driver declares in this capability indicate what it can do when it transmits data. If the driver can only verify checksums when receiving data, then it should not indicate that it supports this capability. Note this does not imply that the hardware is capable of calculating the IPv4 header checksum. When in a driver's transmit function, the driver will be processing a single frame. Note that the flags that are set on it are different from the ones described above and are documented in its manual page. These flags indicate how the driver is expected to program the hardware and what checksumming is required. Not all frames will require hardware checksumming or will ask the hardware to checksum it.

If a driver supports offloading the receive checksum and verification, it should check to see what the hardware indicated was verified. However, each distinct message should have the checksum bits set on it, if applicable. It is recommended that device drivers provide a private property or driver.conf(4) property to control whether or not checksumming is enabled for both rx and tx; however, the default disposition is recommended to be enabled for both. This way if hardware bugs are found in the checksumming implementation, they can be disabled without requiring software updates. At the moment, LSO support is limited to TCP inside of IPv4. This structure has the following members which are used to indicate various types of LSO support. Each flag represents a different form of LSO. Like with checksumming, it is recommended that driver writers provide a means for disabling the support of LSO even if it is enabled by default. This deals with the case where issues that pop up for LSO may be worked around without requiring additional driver work. PROPERTIES Properties in the MAC framework represent aspects of a link. These include things like the link's current state and MTU. Many of the properties in the system are focused around auto-negotiation and controlling what link speeds are advertised. Information about properties is covered by three different device entry points. Many of the properties listed below are read-only. However, driver writers may not implement the ability to set all writable properties. Many of these depend on the card itself. While copper Ethernet often does not have this restriction, it often exists with various fiber standards and phys. The following properties are the subset of MAC framework properties that driver writers should be aware of and handle. While other properties exist in the system, driver writers should always return an error when a property not listed below is encountered.

A duplex link may have traffic flowing in both directions at the same time. This may be because the link has not negotiated to a specific speed or it is down. Communication may travel in only one direction on the link at a given time. Communication may travel in both directions on the link simultaneously. It indicates whether the link is up or down. This may be because of a negotiation problem, a cable problem, or some other device specific issue. If auto-negotiation is in use, it should have completed. Traffic should be able to flow over the link, barring other issues. A value of 0 indicates that auto-negotiation is disabled. A non-zero value indicates that auto-negotiation is enabled. Devices should generally default to enabling auto-negotiation. When getting this property, the device driver should return the current state. When setting this property, if the device supports operating in the requested mode, then the device driver should reset the link to negotiate to the new speed after updating any internal registers. This indicates the maximum size packet that the device can transmit, ignoring its own headers. For an Ethernet device, this would exclude the size of the Ethernet header and any VLAN headers that would be placed. It is up to the driver to ensure that any MTU values that it accepts when adding in its margin and header sizes does not exceed its maximum frame size. By default, drivers for Ethernet should initialize this value and the MTU to 1500. When getting this property, the driver should return its current recorded MTU. Note that the call may fail. If the call completes successfully, the driver should update the hardware with the new value of the MTU and perform any other work needed to handle it. Note, this only describes what this device will advertise. What is actually enabled may be different and is subject to the rules of auto-negotiation. No pause frames should be generated or honored.

When getting this property, the device driver should return the way that it has configured the device, not what the device has actually negotiated. When setting the property, it should update the hardware and allow the link to potentially perform auto-negotiation again. The remaining properties are all about various auto-negotiation link speeds. For any given supported speed, there is one of each. When these are retrieved, they should return the current value of the property. When they are set, they should change how the hardware advertises the specific speed and trigger any kind of link reset and auto-negotiation, if enabled, to occur. They are meant to reflect what has actually been negotiated. See the Link Speed and Auto-negotiation section for more information. Private Properties In addition to the defined properties above, drivers are allowed to define private properties. These private properties are device-specific properties. Properties are distinguished by a name, which is a character string. The driver may define whatever semantics it wants for these private properties. They will not be listed when running dladm(1M), unless explicitly requested by name. All such properties should start with a leading underscore character and then consist of alphanumeric ASCII characters and additional underscores or hyphens. Device drivers should tell the different properties apart by using the strcmp(9F) function to compare it to the set of properties that it knows about. When encountering properties that it doesn't know, it should treat them like all other unknown properties. STATISTICS The MAC framework defines a couple different sets of statistics which are based on various standards for devices to implement. There are both statistics that are required for all devices and then there is a separate set of Ethernet specific statistics. Not all devices will support every statistic. In many cases, several device registers will need to be combined to create the proper stat.

If a device does not support a specific statistic, then it is fine to return that it is not supported. The same should be used for unrecognized statistics. General Device Statistics The following statistics are based on MIB-II statistics from both RFC 1213 and RFC 1573. Ethernet Specific Statistics The following statistics are specific to Ethernet devices. This is a count of packets that were not an integral number of octets and failed the FCS check. This is used for all fiber receivers. This is used for all copper receivers. RECEIVE DESCRIPTOR LAYOUT One of the important things that a device driver must do is lay out DMA memory, generally in a ring of descriptors, into which received Ethernet frames will be placed. When performing this, there are a few things that drivers should generally do: 1. Drivers should lay out memory so that the IP header will be 4-byte aligned. The IP stack expects that the beginning of an IP header will be at a 4-byte aligned address; however, a DMA allocation will be at a 4- or 8-byte aligned address by default. The IP hearder is at a 14 byte offset from the beginning of the Ethernet frame, leaving the IP header at a 2-byte alignment if the Ethernet frame starts at the beginning of the DMA buffer. If VLAN tagging is in place, then each VLAN tag adds 4 bytes, which doesn't change the alignment the IP header is found at. As a solution to this, the driver should program the device to start placing the received Ethernet frame at two bytes off of the start of the DMA buffer. This will make sure that no matter whether or not VLAN tags are present, that the IP header will be 4-byte aligned. 2. Drivers should try to allocate the DMA memory used for receiving frames as a continuous buffer. If for some reason that would not be possible, the driver should try to ensure that there is enough space for all of the initial Ethernet and any possible layer three and layer four headers (such as IP, TCP, or UDP) in the initial descriptor. 3.

As discussed in the MBLKS AND DMA section, there are multiple strategies for managing the relationship between DMA data, receive descriptors, and the operating system representation of a packet in the mblk(9S) structure. Drivers must limit their resource consumption. See the Considerations section of MBLKS AND DMA for more on this. TX STALL DETECTION, DEVICE RESETS, AND FAULT MANAGEMENT Device drivers are the first line of defense for dealing with broken devices and bugs in their firmware. While most devices will rarely fail, it is important that when designing and implementing the device driver that particular attention is paid in the design with respect to RAS (Reliability, Availability, and Serviceability). While everything described in this section is optional, it is highly recommended that all new device drivers follow these guidelines. The Fault Management Architecture (FMA) provides facilities for detecting and reporting various classes of defects and faults. By registering with the fault management framework, a device driver is given the chance to detect and notice transport errors as well as report other errors that exist. Transport Errors Many modern networking devices leverage PCI or PCI Express. Device Indicated Errors Many devices have capabilities to announce to a device driver that a fatal correctable error or uncorrectable error has occurred. Other devices have the ability to indicate that various physical issues have occurred such as a fan failing or a temperature sensor having fired. Drivers should wire themselves to receive notifications when these events occur. The means and capabilities will vary from device to device. For example, some devices will generate information about these notifications through special interrupts. Other devices may have a register that software can poll. Driver Transmit Stall Detection One of the primary responsibilities of a hardened device driver is to perform transmit stall detection.

The core idea behind tx stall detection is that the driver should record when it's getting activity related to when data has been successfully transmitted. Most devices should be transmitting data on a regular basis as long as the link is up. If it is not, then this may indicate that the device is stuck and needs to be reset. At this time, the MAC framework does not provide any resources for performing these checks; however, polling on each individual transmit ring for the last completion time while something is actively being transmitted through the use of routines such as timeout(9F) may be a reasonable starting point. Driver Command Timeout Detection Each device is programmed in different ways. Some devices are programmed through asynchronous commands while others are programmed by writing directly to memory mapped registers. If a device receives asynchronous replies to commands, then the device driver should set reasonable timeouts for all such commands and plan on detecting them. If a timeout occurs, the driver should presume that there is an issue with the hardware and proceed to abort the command or reset the device. Many devices do not have such a communication mechanism. However, whenever there is some activity where the device driver must wait, then it should be prepared for the fact that the device may never get back to it and react appropriately by performing some kind of device reset. Reacting to Errors When any of the above categories of errors has been triggered, the behavior that the device driver should take depends on the kind of error. If a fatal error, for example, a transport error, a transmit stall was detected, or the device indicated an uncorrectable error was detected, then it is important that the driver take the following steps: 1. Set a flag in the device driver's state that indicates that it has hit an error condition.http://www.eau-petit-pont.com/images/breville-bread-maker-manual-br9.pdf