diff for duplicates of <200608162324.47235.arnd@arndb.de> diff --git a/a/1.txt b/N1/1.txt index 81cf777..c252158 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ Am Wednesday 16 August 2006 22:46 schrieb David Miller: > I'm not familiar with the spidernet TX side interrupt capabilities > so I can't say whether that is something that can be directly -> implied. =A0In fact, I get the impression that spidernet is limited +> implied. In fact, I get the impression that spidernet is limited > in some way and that's where all the strange approaches are coming > from :) @@ -15,11 +15,11 @@ sounds like the right approach to simplify the code. The spider hardware offers at least these options: -=2D end of TX queue interrupt -=2D set a per-descriptor bit to fire an interrupt at a specific frame -=2D an interrupt for each frame (may be multiple descriptors) -=2D an interrupt for each descriptor -=2D timers implemented in the spidernet hardware +- end of TX queue interrupt +- set a per-descriptor bit to fire an interrupt at a specific frame +- an interrupt for each frame (may be multiple descriptors) +- an interrupt for each descriptor +- timers implemented in the spidernet hardware We first had an interrupt per descriptor, then got rid of all TX interrupts and replaced them by timers to reduce the interrupt load, diff --git a/a/content_digest b/N1/content_digest index 8bd63c8..6d2a5b0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,19 +5,20 @@ "Subject\0Re: [PATCH 1/2]: powerpc/cell spidernet bottom half\0" "Date\0Wed, 16 Aug 2006 23:24:46 +0200\0" "To\0David Miller <davem@davemloft.net>\0" - "Cc\0akpm@osdl.org" - jeff@garzik.org + "Cc\0jeff@garzik.org" + linas@austin.ibm.com netdev@vger.kernel.org - jklewis@us.ibm.com linux-kernel@vger.kernel.org linuxppc-dev@ozlabs.org - " Jens.Osterkamp@de.ibm.com\0" + jklewis@us.ibm.com + Jens.Osterkamp@de.ibm.com + " akpm@osdl.org\0" "\00:1\0" "b\0" "Am Wednesday 16 August 2006 22:46 schrieb David Miller:\n" "> I'm not familiar with the spidernet TX side interrupt capabilities\n" "> so I can't say whether that is something that can be directly\n" - "> implied. =A0In fact, I get the impression that spidernet is limited\n" + "> implied. \302\240In fact, I get the impression that spidernet is limited\n" "> in some way and that's where all the strange approaches are coming\n" "> from :)\n" "\n" @@ -31,11 +32,11 @@ "\n" "The spider hardware offers at least these options:\n" "\n" - "=2D end of TX queue interrupt\n" - "=2D set a per-descriptor bit to fire an interrupt at a specific frame\n" - "=2D an interrupt for each frame (may be multiple descriptors)\n" - "=2D an interrupt for each descriptor\n" - "=2D timers implemented in the spidernet hardware\n" + "- end of TX queue interrupt\n" + "- set a per-descriptor bit to fire an interrupt at a specific frame\n" + "- an interrupt for each frame (may be multiple descriptors)\n" + "- an interrupt for each descriptor\n" + "- timers implemented in the spidernet hardware\n" "\n" "We first had an interrupt per descriptor, then got rid of all TX\n" "interrupts and replaced them by timers to reduce the interrupt load,\n" @@ -48,4 +49,4 @@ "\n" "\tArnd <><" -46ecd106138c8121baf957027da4a9be670a2803d67710e315a2d52e898ec3b4 +0ec7fcd654a9e45f7804a12eade660c8d086a6dadf061b62b3dc1fc5faa26ca3
diff --git a/a/1.txt b/N2/1.txt index 81cf777..c252158 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,7 +1,7 @@ Am Wednesday 16 August 2006 22:46 schrieb David Miller: > I'm not familiar with the spidernet TX side interrupt capabilities > so I can't say whether that is something that can be directly -> implied. =A0In fact, I get the impression that spidernet is limited +> implied. In fact, I get the impression that spidernet is limited > in some way and that's where all the strange approaches are coming > from :) @@ -15,11 +15,11 @@ sounds like the right approach to simplify the code. The spider hardware offers at least these options: -=2D end of TX queue interrupt -=2D set a per-descriptor bit to fire an interrupt at a specific frame -=2D an interrupt for each frame (may be multiple descriptors) -=2D an interrupt for each descriptor -=2D timers implemented in the spidernet hardware +- end of TX queue interrupt +- set a per-descriptor bit to fire an interrupt at a specific frame +- an interrupt for each frame (may be multiple descriptors) +- an interrupt for each descriptor +- timers implemented in the spidernet hardware We first had an interrupt per descriptor, then got rid of all TX interrupts and replaced them by timers to reduce the interrupt load, diff --git a/a/content_digest b/N2/content_digest index 8bd63c8..2dbae61 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -17,7 +17,7 @@ "Am Wednesday 16 August 2006 22:46 schrieb David Miller:\n" "> I'm not familiar with the spidernet TX side interrupt capabilities\n" "> so I can't say whether that is something that can be directly\n" - "> implied. =A0In fact, I get the impression that spidernet is limited\n" + "> implied. \302\240In fact, I get the impression that spidernet is limited\n" "> in some way and that's where all the strange approaches are coming\n" "> from :)\n" "\n" @@ -31,11 +31,11 @@ "\n" "The spider hardware offers at least these options:\n" "\n" - "=2D end of TX queue interrupt\n" - "=2D set a per-descriptor bit to fire an interrupt at a specific frame\n" - "=2D an interrupt for each frame (may be multiple descriptors)\n" - "=2D an interrupt for each descriptor\n" - "=2D timers implemented in the spidernet hardware\n" + "- end of TX queue interrupt\n" + "- set a per-descriptor bit to fire an interrupt at a specific frame\n" + "- an interrupt for each frame (may be multiple descriptors)\n" + "- an interrupt for each descriptor\n" + "- timers implemented in the spidernet hardware\n" "\n" "We first had an interrupt per descriptor, then got rid of all TX\n" "interrupts and replaced them by timers to reduce the interrupt load,\n" @@ -48,4 +48,4 @@ "\n" "\tArnd <><" -46ecd106138c8121baf957027da4a9be670a2803d67710e315a2d52e898ec3b4 +4f0cfd8199c605c9e2ae9322398590aa5a331f80415010812ceb72d26ca8d053
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.