Buffering non-posted read commands and responses

• US 20040024947A1
• Filed: 11/01/2002
• Published: 02/05/2004
• Est. Priority Date: 07/31/2002
• Status: Active Grant

• Current Assignee: Advanced Micro Devices, Inc.
• Original Assignee: Advanced Micro Devices, Inc.
• Inventors: Miranda, Paul, Hewitt, Larry, Barth, Frank, Winkler, Joerg
• Granted Patent: US 8,244,950 B2
• Time in Patent Office: Days
• US Class Current: 710/310
• CPC Class Codes: G06F 13/4059 where the synchronisation uses buffers, e.g. for speed matching between buses

Abstract

An improved interface technique for use in a southbridge or I/O hub or in similar devices is provided where non-posted read requests are received from at least one requestor, and upstream commands based on these requests are transmitted. Response data is received in reply to commands that were previously transmitted, and responses are transmitted to the at least one requester based on the response data. A buffer unit is provided for storing command identification data that identifies commands that were already transmitted or that are still to be transmitted, and response availability data that specifies response data that has been received by the receive engine. The improvement may enable multiple outstanding read requests.

Claims

1. A southbridge device comprising:

a transmit engine adapted to receive non-posted read requests from at least one requestor, and transmit upstream commands based on said non-posted read requests;

a receive engine adapted to receive response data in reply to commands previously transmitted by said transmit engine, and transmit responses to said at least one requestor based on said response data; and

a buffer unit connected to said transmit engine and said receive engine, said buffer unit being adapted to store command identification data identifying commands transmitted or to be transmitted by said transmit engine, and response availability data specifying response data that has been received by said receive engine.

2. The southbridge device of claim 1, wherein said command identification data includes said identified commands transmitted or to be transmitted by said transmit engine.

3. The southbridge device of claim 1, wherein said buffer unit is arranged to store command identification data identifying plural commands each relating to the same requestor.

4. The southbridge device of claim 1, wherein said transmit engine is capable of transmitting upstream commands based on plural non-posted read requests from one requestor, irrespective of the availability of responses to said requests.

5. The southbridge device of claim 4, wherein said transmit engine is capable of transmitting said upstream commands based on bursts of non-posted read requests.

6. The southbridge device of claim 1, wherein said buffer unit is arranged to store command identification data identifying plural commands each relating to different requestors.

7. The southbridge device of claim 1, wherein said non-posted read requests are memory read requests.

8. The southbridge device of claim 1, further comprising:

an interface unit connected to said transmit engine and said receive engine for transmitting said upstream commands and receiving said response data via a data link that supports split transactions.

9. The southbridge device of claim 8, wherein said data link that supports split transactions is a HyperTransport compliant data link.

10. The southbridge device of claim 1, comprising said at least one requestor.

11. The southbridge device of claim 1, wherein said at least one requestor is a hard disc controller.

12. The southbridge device of claim 1, wherein said at least one requestor is an ethernet controller.

13. The southbridge device of claim 1, wherein said at least one requestor is a USB (Universal Serial Bus) controller.

14. The southbridge device of claim 1, wherein said at least one requestor is an audio codec controller.

15. The southbridge device of claim 1, wherein said transmit engine is adapted to receive non-posted read requests from at least two requestors, and wherein said transmit engine is adapted to arbitrate between said at least two requestors when transmitting said upstream commands.

16. The southbridge device of claim 1, wherein said transmit engine is adapted to write said command identification data into said buffer unit when receiving said non-posted read requests.

17. The southbridge device of claim 1, wherein said transmit engine is adapted to write said command identification data into said buffer unit when transmitting said upstream commands.

18. The southbridge device of claim 1, wherein said receive engine is adapted to generate said response availability data and write the generated response availability data into said buffer unit when receiving said response data.

19. The southbridge device of claim 1, wherein said receive engine is adapted to clear response availability data in said buffer unit when transmitting respective responses.

20. The southbridge device of claim 1, being an I/O (Input/Output) hub.

21. An integrated circuit chip comprising:

a transmit circuit adapted to receive non-posted read requests from at least one requestor, and transmit upstream commands based on said non-posted read requests;

a receive circuit adapted to receive response data in reply to commands previously transmitted by said transmit circuit, and transmit responses to said at least one requester based on said response data; and

a buffer unit connected to said transmit circuit and said receive circuit, said buffer unit being adapted to store command identification data identifying commands transmitted or to be transmitted by said transmit circuit, and response availability data specifying response data that has been received by said receive circuit.

22. A computer system comprising:

at least one peripheral component; and

a southbridge comprising a transmit engine adapted to receive non-posted read requests from at least one peripheral component controller, and transmit upstream commands based on said non-posted read requests; and

a receive engine adapted to receive response data in reply to commands previously transmitted by said transmit engine, and transmit responses to said at least one peripheral component controller based on said response data;

wherein said southbridge further comprises a buffer unit connected to said transmit engine and said receive engine, said buffer unit being adapted to store command identification data identifying commands transmitted or to be transmitted by said transmit engine, and response availability data specifying response data that has been received by said receive engine.

23. A method of operating a southbridge device, the method comprising:

receiving non-posted read requests from at least one requester;

transmitting upstream commands based on said non-posted read requests;

receiving response data in reply to previously transmitted commands; and

transmitting responses to said at least one requestor based on said response data,

wherein the method further comprises;

storing command identification data identifying transmitted or to be transmitted commands; and

storing response availability data specifying received response data.

24. The method of claim 23, wherein said command identification data includes said identified transmitted or to be transmitted commands.

25. The method of claim 23, wherein said command identification data identifies plural commands each relating to the same requestor.

26. The method of claim 23, wherein said upstream commands are transmitted based on plural non-posted read requests from one requestor, irrespective of the availability of responses to said requests.

27. The method of claim 26, wherein said upstream commands are transmitted based on bursts of non-posted read requests.

28. The method of claim 23, wherein said command identification data identifies plural commands each relating to different requestors.

29. The method of claim 23, wherein said non-posted read requests are memory read requests.

30. The method of claim 23, wherein transmission of said upstream commands and reception of said response data are performed via a data link that supports split transactions.

31. The method of claim 30, wherein said data link that supports split transactions is a HyperTransport compliant data link.

32. The method of claim 23, wherein reception of said non-posted read requests and transmission of said responses are performed from and to requestors incorporated in said southbridge device.

33. The method of claim 23, wherein said at least one requestor is a hard disc controller.

34. The method of claim 23, wherein said at least one requester is an ethernet controller.

35. The method of claim 23, wherein said at least one requester is a USB (Universal Serial Bus) controller.

36. The method of claim 23, wherein said at least one requestor is an audio codec controller.

37. The method of claim 23, wherein said non-posted read requests are received from at least two requesters, and the method further comprises:

arbitrating between said at least two requestors when transmitting said upstream commands.

38. The method of claim 23, further comprising:

writing said command identification data into a buffer when receiving said non-posted read requests.

39. The method of claim 23, further comprising:

writing said command identification data into a buffer when transmitting said upstream commands.

40. The method of claim 23, further comprising:

generating said response availability data; and

writing the generated response availability data into a buffer when receiving said response data.

41. The method of claim 23, further comprising:

clearing response availability data when transmitting respective responses.

42. The method of claim 23, for operating an I/O (Input/Output) hub.