From: Kevin Krakauer <krakauer@google.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
dmaengine@vger.kernel.org
Subject: Re: idxd: shared workqueues and dmaengine
Date: Thu, 27 Mar 2025 11:56:24 -0700 [thread overview]
Message-ID: <Z-WfWC63NbzoU_kk@google.com> (raw)
In-Reply-To: <3a28b0a6-3c7c-43b9-a592-111692d3c1bf@intel.com>
On Wed, Mar 26, 2025 at 05:15:37PM -0700, Dave Jiang wrote:
> So I think maybe a new sysfs attribute can be added to wq to allow the user to choose whether to make the channel DMA_PRIVATE or not. By default it can be set to DMA_PRIVATE to keep legacy behavior. I think that should solve the issue you are encountering?
Yep, that would do it. Thanks for helping me understand -- I was
wondering whether I was missing something.
Easy for me to workaround for now, or maybe I'll just add the sysfs
attribute and send it to the list. Thanks!
next prev parent reply other threads:[~2025-03-27 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 0:05 idxd: shared workqueues and dmaengine Kevin Krakauer
2025-03-27 0:15 ` Dave Jiang
2025-03-27 18:56 ` Kevin Krakauer [this message]
2025-03-27 20:22 ` Dave Jiang
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=Z-WfWC63NbzoU_kk@google.com \
--to=krakauer@google.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox