From: trem <tremyfr@yahoo.fr>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix
Date: Tue, 20 Nov 2007 23:09:53 +0100 [thread overview]
Message-ID: <47435B31.2070304@yahoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0711161214480.24276@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Fri, 16 Nov 2007, Nelson, Shannon wrote:
>> first->async_tx.phys;
>>> - __list_splice(&new_chain, ioat_chan->used_desc.prev);
>>> + list_splice_tail(&new_chain, ioat_chan->used_desc.prev);
>>>
>> NAK.
>>
>> These functions do insertions differently. The 'prev' is pointing to
>> the last valid descriptor in the queue and you really want to get the
>> new_chain stuck on after this. Your list_splice_tail() will insert the
>> new_chain just before it which will muck up the order of the DMA
>> requests.
>>
>> You might have more success with
>> list_splice_tail(&new_chain, ioat_chan->used_desc);
>> where used_desc points to the whole list, rather than using the .prev
>> pointer to a specific node.
>>
>> Please copy me on future ioatdma related comments.
>>
>
> And people wonder why we post RT related patches to LKML. This is exactly
> why!
>
> Thanks for the response Shannon!
>
> -- Steve
>
Hi
I've tried this change, but it still don't compile. So I propose this patch.
regards,
trem
------------------------
Index: linux-2.6.23/drivers/dma/ioat_dma.c
===================================================================
--- linux-2.6.23.orig/drivers/dma/ioat_dma.c
+++ linux-2.6.23/drivers/dma/ioat_dma.c
@@ -244,7 +244,7 @@ static dma_cookie_t ioat_tx_submit(struc
/* write address into NextDescriptor field of last desc in chain */
to_ioat_desc(ioat_chan->used_desc.prev)->hw->next =
first->async_tx.phys;
- __list_splice(&new_chain, ioat_chan->used_desc.prev);
+ list_splice_tail(&new_chain, &ioat_chan->used_desc);
ioat_chan->pending += desc_count;
if (ioat_chan->pending >= 4) {
next prev parent reply other threads:[~2007-11-20 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 17:07 [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix Nelson, Shannon
2007-11-16 17:16 ` Steven Rostedt
2007-11-20 22:09 ` trem [this message]
2007-12-15 3:56 ` [PATCH][RT] 2.6.24-rc5-rt1 " Sven-Thorsten Dietrich
2007-12-15 14:05 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 11:57 [PATCH][RT] 2.6.24-rc2-rt1 " Sven-Thorsten Dietrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47435B31.2070304@yahoo.fr \
--to=tremyfr@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.