From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Chris Leech <christopher.leech@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/9] I/OAT
Date: Thu, 30 Mar 2006 10:21:24 +0400 [thread overview]
Message-ID: <20060330062124.GA8545@2ka.mipt.ru> (raw)
In-Reply-To: <1143672844.27644.5.camel@black-lazer.jf.intel.com>
On Wed, Mar 29, 2006 at 02:54:04PM -0800, Chris Leech (christopher.leech@intel.com) wrote:
> [I/OAT] Driver for the Intel(R) I/OAT DMA engine
>
> From: Chris Leech <christopher.leech@intel.com>
>
> Adds a new ioatdma driver
>
> Signed-off-by: Chris Leech <christopher.leech@intel.com>
Let's do it again.
Could you please describe how struct ioat_dma_chan channels are freed?
For example when device is removed just after it has been added.
ioat_probe() -> enumerate_dma_channels() (failures are ok now) ->
kmalloc a lot of channels.
ioat_remove() -> dma_async_device_unregister() which does not cleanup
ioat_dma_chan channels, but only clients.
It ends up in dma_async_device_cleanup() only.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2006-03-30 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 22:54 [PATCH 2/9] I/OAT Chris Leech
2006-03-30 6:21 ` Evgeniy Polyakov [this message]
2006-03-31 19:04 ` Chris Leech
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=20060330062124.GA8545@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=christopher.leech@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).