• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Tcp performance Final Report
 

Tcp performance Final Report

on

  • 612 views

Tcp performance Final Report

Tcp performance Final Report

Statistics

Views

Total Views
612
Views on SlideShare
612
Embed Views
0

Actions

Likes
2
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Tcp performance Final Report Tcp performance Final Report Document Transcript

    • CHAPTER 1 INTRODUCTION Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 1. INTRODUCTION1.1 SYSTEM OVERVIEW Advances in optical network technology enable fast pace increase inphysical bandwidth whose growth rate has far surpassed that of other resourcessuch as CPU and memory bus. This phenomenon causes network bottlenecks toshift from bandwidth to other resources. The rise of new applications thatrequire in-network processing hastens this shift, too. For instance, a voice-over-IP call made from a cell phone to a PSTN phone must go through a mediagateway that performs audio transcoding “on the fly” as the two end pointsoften use different audio compression standards. Examples of in-networkprocessing services are increasingly abundant from security, performance-enhancing proxies (PEP), to media translation. These services add additionalloads to processing capacity in the network components. New routertechnologies such as extensible routers or programmable routers also need to Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • deal with scheduling of CPU usage per packet as well as bandwidth usage perpacket1.2 OBJECTIVE OF THE PROJECTOur objective is to reduce both bandwidth and CPU Process whichcan be a bottleneck for network flow1.3 LITERATURE SURVEY1.3.1 Existing System In existing system conventional TCP/AQM schemes can significantlylose throughput and suffer harmful unfairness in this environment, particularlywhen CPU cycles become scarcer.1.3.2 Proposed SystemThe proposed system we establish a notion of dual-resource proportionalfairness and propose an AQM scheme, called Dual-Resource Queue (DRQ),that can closely approximate proportional fairness for TCP Reno sources within-network processing requirements.1.4 ORGANISATION OF THE REPORT Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The Chapter 1 presents the review of Literature. The goal tended to beattained in the project is explained in the objectives. The problem descriptiontell the need for the system and its purpose for the users community. TheChapter 2 explains the system requirement for both by feature and byfunctionality hierarchy. The Chapter 3 describes the System Design whichincludes the decomposition description, dependency description and detaileddesign of modules. The Chapter 4 describes the implementation of the project, whichincludes the modules and components used in this project. The Chapter 5 dealswith the test plan and testing of the project. The Chapter 6 describes the resultof the implementations. The Chapter 7 contains the conclusion of the workdone and also the extension of the work. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CHAPTER 2SOFTWARE REQUIREMENT SPECIFICATION Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 2. SOFTWARE REQUIREMENT SPECIFICATION1.2.1 EXTERNAL INTERFACE REQUIREMENTS2.1.1User Interfaces The product must be usable from the text command line, particularlyunder operating systems where the command line is a standard common userinterface (such as Linux). However, some guidelines do apply:Help: Help should be available for all tools. Command – line tools shouldprint a helpful message (if appropriate) If invoked with no arguments (ifany command line tools are designed to accept input as a pipe, it is acceptableto forego this rule). If multiple options are available,the product shouldpresent a text menu detailing the probable choices rather than forcing theuser to retype everything up to that point. All command-line tools must print asummary of use and available subcommands if invoked with invalid ormissing arguments. GUI tools must have help available from any screen, either Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • via a button, context-sensitive help, or a summary of help on the page (webforms may take the latter route).Feedback: Each tool should give feedback to the user describing the resultsof their last action; in other words, issue for submissions should be aacknowledged (with a response message from standard output, a follow-onweb page, or return email) with some positive indication of the result ("Yourissue has been reported and filed with ID 523", for example). If preconditionsfor an action have not been met (an issue is filed with an invalid orinappropriate a format, for example, or the user is not of a class allowed toperform these actions) the feedback should indicate that the desired action hasnot been accomplished & give an indication of the error and how it could befixed.Command-line options: If command - line tools can accept arguments, theywill support them according to the standards laid out in the GNU codingstandards, and should support both short and long forms.2.1.2 Hardware Interfaces Simulation should be implemented in a hardware-independent fashionand should not rely on any particular hardware interfaces. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 2.1.3 Software Interfaces No software interfaces except for the Python subsystem arenecessary. The issue is repository will be held on-disk in the form of XML filesstored in a directory tree. The repository will be labeled network simulation-repository and will a hold the following subdirectories:2.1.3.1 Awaiting - Review This directory holds issue reports which are awaiting a review beforebeing added to the database proper. The awaiting-review subdirectory isparticularly useful when a repository is set up such that all issue reports mustpass through one or more issue managers before being accepted into thedatabase.2.1.3.2 Network Simulation-Options This directory holds various files meant to customize or augment thebehaviour of the product.2.1.3.3 Templates Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • This directory holds the XML document type definitions (DTDs) for thevarious issue types that the repository will track2.1.4 Communications Interfaces When the "external user" user class is included, a Network simulationshould allow submissions viastandard email and via the world wide web( probably using CGI scripting). No other communications interfaces aremandated.2.2.2 SYSTEM FEATURES The system should provide the full fill text of a submitted issue on arequest by the command network simulation cat template-name issue-id2.2.1 Stimulus/Response SequencesDescription The user queries the database by using the command network simulationquery issue-template match-expression; the system scan the submitted issuesunder the given template and returns feedback according to the match-expression. Match expressions will be in the format of a subset of XPath orXQL. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • RequiresAn installed database with read accessEnsuresA resultant list of matching ids and feedbackPriority and Frequency of UseThe priority and frequency of use is high.3.2.3 OTHER NONFUNCTIONAL REQUIREMENTS3.13.2Performance RequirementsThe system has no specific performance requirements at this time3.3Safety Requirements The system has no specific safety requirements at this time, except to theextent that it is designed to run without root access.3.4Security Requirements The system has no specific security requirements at this time. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 3.5Software Quality AttributesNo additional software quality attributes are addressed in the requirementsat this time.3.6Business Rules There are no explicit business rules for operation of Network simulationat this time. All users with access to the command line tools and a copy of therepository will be allowed to perform all actions. Additional securitymeasures and procedures may be added at a future date. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CHAPTER 3SOFTWARE DESIGN DOCUMENT Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 3. SOFTWARE DESIGN DOCUMENT3.1SYSTEM ARCHITECTURE souece gateway Fig 3.1 System Architecture Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The architecture contains the sender , receiver connected in the networkand the service gateway in traffic engineering console . The source nodeconnects with the destination node. After the connecting the nodes , choose thefile to be send from source to to transfer the data and justified the best path tosend the data using red algoritham.tcp/aqm are used in the traffic network toredused the traffic3.1.1 Use Case Diagram Fig 3.2: Use Case Diagram Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The use case diagram gives the primary elements and the process of theproject. The primary elements are actor the “actor” and the process of the “usecase”. Use case diagram show the actor and the use case of the projectwhich interact with each other. The use case diagram describes the basicprocess of the entire network system. In this project, userand receiver are themajor actor who performs all the actions such as connecting the node andsending the file via the service gate way to receiver.3.1.2 State diagram Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Fig:3.3: State Diagram Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The State diagram gives the information flow of the project.First theuser uploads the files and it is converted then it is stored in file system onplay option the file is fetched from the file system and played.3.1.4 Component Diagram Fig 3.4 : Component Diagram Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The Component Diagram gives the high-level parts of the system that makesthe system. In this project the high-level parts are the interface where the senderand receiver can interact through the system.3.2 DECOMPOSITION DESCRIPTION3.2.1 Module Decompostion The various modules that are used in the project are listed below andexplained in details .the various modules are explained briefly with all appliedinput got corresponding to these modules .they are• network module• packet scheduling• bandwidth sharing3.2.1.1 Network Module Client-server computing or networking is a distributed applicationarchitecture that partitions tasks or workloads between service providers(servers) and service requesters, called clients. Often clients and servers operateover a computer network on separate hardware. A server machine is a high-performance host that is running one or more server programs which share itsresources with clients. A client also shares any of its resources; Clientstherefore initiate communication sessions with servers which await (listen to)incoming requests. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Fig 3.5 : CPU Cycle Process3.2.1.2 Packet Scheduling This packet scheduling policy is simple to implement, and yields goodperformance in the common case that node schedules are known, andinformation about node availability is accurate. A potential drawback is that anode crash (or other failure event) can lead to a number of wasted RTSs to thefailed node. When added across channels, the number may exceed the limit of 7retransmission attempts allowed for a single channel in the IEEE 802.113.2.1.3 BANDWIDTH SHARING Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Approach where each node requests and grants as much bandwidth aspossible at each turn. Additionally, we compare the RENO algorithm for packetscheduling to a First-In-First-Out (FIFO) scheduler where all the SDUs with thesame next-hop are enqueued into the same buffer. For this purpose we simulatea network with an increasing number of nodes, from 2 to 10, arranged in a chaintopology. Each node has one traffic flow directed to the chain end-point node,carried with a constant bit-rate stream of 1000 bytes packets emulating infinitebandwidth demands. Congestion control has been extensively studied fornetworks running a single protocol. However, when sources sharing the samenetwork react to different congestion signals, the existing duality model nolonger explains the behavior of bandwidth allocation. The existence anduniqueness properties of equilibrium in heterogeneous protocol case areexamined.RED ALGORITHM Calculating avg queue size If(avg<THmin) queue packet Else if(THmin<=avg<=THmax) Calculate pa with pa Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • discard packet else with probability(1- pa ) queue packet Else if (avg>=THmax) discard packet3.2.2 Process DecompositionCreating a Tcp Reno Interface This process is creating tcp reno for getting data and store the data . Itcollect all send data and order wise send to receiver ma.Selecting and placing the service Node The gateway has been selected based on the shortest path and cost. And itis send data to receiver.Sending the Packet The sender can browse any of the file from the local host . As soon as thefile has selected and it display the connect in the scrolling window and transfersthe packet to the destination.3.2.3 Dependency DescriptionInter Module Dependency The network client in networking module is the one that dependent onother modules. This module connects all clients and display the informationpresent in the modules.Inter Process Dependency Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • All the processes are dependent on process . all process are started fromthe gateway interface section in process 1.3.2HUMAN INTERFACE DESIGN3.3.1 Screen Image The administrator can interact with the client using the interface iscreated using ns 2 tools. The interface designed as by clicking the button theinformation of the client is obtained in the screen of the administrator sothe user and node details of the system can be managed efficiently Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Fig 3.6 :Screen Chat Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CHAPTER 4IMPLEMENTATION Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 4. IMPLEMENTATION4.1 MODULE WISE IMPLEMENTATION Congestion control in network traffic is basically implemented inLINUX system and using ns2 transferring the data from sender to receiver.Module 1: Network Modulea network that consists of a set of unidirectional links, Client-server computingor networking is a distributed application architecture that partitions tasks orworkloads between service providers (servers) and service requesters, calledclients. Often clients and servers operate over a computer network on separatehardware. A server machine is a high-performance host that is running one ormore server programs which share its resources with clients. A client also Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • shares any of its resources; Clients therefore initiate communication sessionswith servers which await (listen to) incoming requestsPACKET SCHEDULING This packet scheduling policy is simple to implement, and yields goodperformance in the common case that node schedules are known, andinformation about node availability is accurate. A potential drawback is that anode crash (or other failure event) can lead to a number of wasted RTSs to thefailed node. When added across channels, the number may exceed the limit of 7retransmission attempts allowed for a single channel in the IEEE 802.11 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Step 1: Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Fig 4.1 : send dataThis first step for the process, more sender send the data to thereceiver . Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Strep 2 : Fig 4.2 : Gateway Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • In this section use the gateway. It is interface between sender andreceiver the gateway are collecting the data and send to the Tcp reno. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Step 3 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Fig 4.3 :Use TCP RenoThe final section is TCP reno operation it is collection of dataand order and sequence wise send data to the receiver. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CHAPTER 5TEST PLAN AND TESTING Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 5. TEST PLAN AND TESTING5.1 Testing Testing is the process of analyzing the system for any possible errors, andthereby providing solutions to process solutions to correct them. Inspections areformal group of activities where participants manually examine the code forerrors. It can also be stated as the process of validating and verifying that asoftware program or product meets the business and technical requirements. This process is done by arriving at various test cases that are applied tothe system and the resulting messages being noted. This project performsfollowing testing: • Unit testing Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • • Integration testing • Validating testing5.2 Testing Objectives Testing is the process of executing a program with the intent of findingan error. A test case is the specific scenario of transaction,queries or navigationpaths that represent typical,critical or abnormal use of the system. The test caseshould be repeatable,so that it can be returned as new version of the softwareare used. Test case need to determine that new software works with otherexisting software with which it must share data. The successful test case is theone which uncovers the undiscovered error. In this system Testing is done on each smallest unit possible and theintegration Testing is done to check whether the system is capable of workingwith the other dependency modules. Finally the validation testing is done forchecking whether the system satisfy the users requirements.5.3 UNIT TESTING The first Testing to be performed on the system is Unit Testing. Thistesting involves independent analysis of the system in parts. The mainadvantage gained by performing this testing is high level of accuracy in findingerrors at each phase of the system. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • The Unit Testing is performed in this system by giving input to thesmallest unit or part of the system and expect the desired output if the systemdoesnt produce the Expected output then the system has fault if the expectedoutput is produced then the system works well. The Unit Testing for the system is done for the following units  Network Module  Tcp/Aqm Module  Conversion ModuleS.N FUNCTIONS SAMPLE EXPECTED OBSERVE STATUS Error o. INPUT RESULTS D RESULT Messages 1 Send function Text Received Received Success Null2 Send function Image Received Received Success Null3 Send function Video Received Received Success Null4 Send function Multiple Error Received Failure Invalid concurrent Declaration files5 Send function Corrupt File Error Received Failure Invalid Declaration6 Send function Exe file Error Error Failure Null7 Receive function File Received Received Failure Error:Invali file d path Table 5.1: Unit Testing on Congestion Control Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 5.3.1. Unit Testing on Network ModuleThe unit testing is performed on the upload module by uploading files ofvarying size and varying type. The directory of storing the file was changed andperformed the upload operation. The testing was performed for protect functionand checked whether the the desired output is received. The Test case includemost often input scenario and the system is tested the idea behind the Unittesting is to get the clear picture of the system functionalities. The size and thetype of file it can accept and also the constraints can be analysed in this part.5.2 INTEGRATION TESTING Integration testing is a phase of software testing in which individualsoftware modules are combined and tested as a group. Integration testingfollows unit testing.S.No. FUNCTIO SAMPLE EXPECTE OBSERVED STATUS Error NS INPUT D RESULT RESULTS Messages1 Send File Sent Sent Success Null Function2 Receive File Sent Sent Success Null Function3 Error Corrupted file Error Error message Success Null Function message4 Control File Warning Warning Success Null Function message message5 Control Corrupted Warning Controlled Failure Corupted file Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Function File message not found6 Send Unsupported file Warning File failed Failure Error: File Function format Message content cannot be displayed Table 5.2: Integration Testing on Congestion Control CHAPTER 6 RESULTS AND OBSERVATIONS Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 6. RESULTS AND OBSERVATIONSThe result of the project is that the congestion control for processingconstrained networks. Here reduce both bandwidth and CPU Process whichcan be a bottleneck for network flow6.1 ADVANTAGEAdvances in network technology enable fast pace increase in physicalbandwidth whose growth rate has far surpassed that of other resources such asCPU and memory bus. This phenomenon causes network bottlenecks to shift Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • from bandwidth to other resources. The rise of new applications that requirein-network processing hastens this shift,too. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CHAPTER 7CONCLUSION AND EXTENSION OF WORK Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 7. CONCLUSION AND EXTENSION OF WORKHave shown that under DRQ the average equilibrium throughput for TCP Renosources becomes proportionally fair in the dual-resource environment.Moreover, such an equilibrium is unique and almost always exists, morespecifically, as long as the per-flow steady-state average TCP window size (orper-flow bandwidth-delay product) is sustainable at a value greater than orequal to 2 packets. DRQ significantly outperforms RED-RED scheme whilemaintaining a certain level of fairness. DRQ is scalable to a large number offlows and incrementally deployable since it does not require any change in end-host TCP stacks and builds on an ordinary RED queue. The throughput gainachieved by DRQ over RED-RED comes mostly from two features of itsmarking scheme. The weighted marking at a CPU queue (in proportion toprocessing densities of flows) yields fair sharing of CPU cycles whenever thisresource is scarce, which consequently, results in overall throughput increase.Second, the inter-resource marking, which is a unique feature of DRQ, givesextra penalty to flows that traverses more number of resources, which alsoresults in overall throughput increase. We show by simulation that even apartial deployment of DRQ is beneficial to increasing performance when it isimplemented on a few selected locations where special innetwork processingservices (e.g., media translation, protocol conversion, security and PEP) areenabled. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • APPENDIX Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Table A-1. Requirements Traceability MatrixFunctional Requirement Implemented in Tested inCAT.FR1 ../src/cat.ns:23 test_plan.sgm:429CAT.FR2 ../src/cat.ns:33 test_plan.sgm:438CAT.FR3 ../src/cat.ns:53 test_plan.sgm:448 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CGI.CHANGE-HTML- ../src/html_substitutor.ns:20 test_plan.sgm:753TEMPLATES.FR1CGI.CHANGE-HTML- ../src/html_substitutor.ns:45 test_plan.sgm:753TEMPLATES.FR2CGI.CHANGE-HTML- ../src/html_substitutor.ns:48 test_plan.sgm:754TEMPLATES.FR3CGI.CHANGE-HTML- ../src/html_substitutor.ns:54 test_plan.sgm:754TEMPLATES.FR4CGI.EDIT.FR1 ../src/cgi_switchboard.ns:208 test_plan.sgm:998CGI.EDIT.FR2 ../src/cgi_edit_form.ns:27 test_plan.sgm:1012CGI.EDIT.FR3 ../src/cgi_edit_form.ns:30 test_plan.sgm:1005 ../src/cgi_edit_form.ns:34CGI.EDIT.FR4 ../src/cgi_edit_form.ns:43 test_plan.sgm:1012CGI.EDIT.FR5 ../src/cgi_edit_results.ns:60 test_plan.sgm:1021CGI.FREEQUERY.FR1 ../src/cgi_switchboard.ns:201 test_plan.sgm:853 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • CGI.FREEQUERY.FR3 ../src/cgi_free_query_output.ns:107 test_plan.sgm:859CGI.FREEQUERY.FR4 ../src/cgi_free_query_output.ns:73 test_plan.sgm:859CGI.FREEQUERY.FR5 ../src/cgi_free_query_output.ns:77 test_plan.sgm:859CGI.FREEQUERY.FR6 ../src/cgi_free_query_output.ns:109 test_plan.sgm:859CGI.LIST.FR1 ../src/cgi_switchboard.ns:24 test_plan.sgm:793CGI.LIST.FR2 ../src/cgi_cat_output.ns:79 test_plan.sgm:799CGI.LIST.FR3 ../src/issue_to_html_transformer.ns:54 test_plan.sgm:799CGI.LIST.FR4 ../src/cgi_cat_output.ns:47 test_plan.sgm:818CGI.QUERY.FR1 ../src/cgi_switchboard.ns:119 test_plan.sgm:901CGI.QUERY.FR2 ../src/query_form_generator.ns:15 test_plan.sgm:901CGI.QUERY.FR3 ../src/query_form_generator.ns:36 test_plan.sgm:910 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • Ambit lick SolutionsMail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • REFERENCES 7. References1. Y. Gottlieb and L. Peterson, “A comparative study of extensible routers,” in Proc. of IEEE OpenArch, June 2002, pp. 51–62.2. G. Memik, M. Smith, and W. Hu, “NetBench: A benchmarking suite for network processors,” in Proc. of IEEE International Conference on Computer-Aided Design, San Jose, CA, Nov. 2006 Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com
    • 3. S. Chong, M. Shin, J. Mo, and H.-W. Lee, “Flow control with processing constraint,” IEEE Commun. Lett., 2005, to be published. Ambit lick Solutions Mail Id : Ambitlick@gmail.com , Ambitlicksolutions@gmail.Com