From: Tom Tucker <tom@opengridcomputing.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Tom Tucker <tom@ogc.us>,
bfields@fieldses.org, linux-nfs@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/2] svcrdma: Change DMA mapping logic to avoid the page_address kernel API
Date: Wed, 17 Nov 2010 23:26:59 -0600 [thread overview]
Message-ID: <4CE4B923.6030102@opengridcomputing.com> (raw)
In-Reply-To: <AANLkTik0LkdD-Gm0FAZ-KDS605ZGTewbfejC3GEOK=2x@mail.gmail.com>
On 11/16/10 1:39 PM, Or Gerlitz wrote:
> Tom Tucker<tom@ogc.us> wrote:
>
>> This patch changes the bus mapping logic to avoid page_address() where necessary
> Hi Tom,
>
> Does "when necessary" comes to say that invocations of page_address
> which remained in the code after this patch was applied are safe and
> no kmap call is needed?
That's the premise. Please let me know if something looks suspicious.
Thanks,
Tom
> Or.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-18 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 20:33 [PATCH 0/2] svcrdma: NFSRDMA Server fixes for 2.6.37 Tom Tucker
2010-10-12 20:33 ` [PATCH 1/2] svcrdma: Change DMA mapping logic to avoid the page_address kernel API Tom Tucker
2010-11-16 19:39 ` Or Gerlitz
2010-11-18 5:26 ` Tom Tucker [this message]
2010-10-12 20:33 ` [PATCH 2/2] svcrdma: Cleanup DMA unmapping in error paths Tom Tucker
[not found] ` <20101012203332.22154.37230.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-10-19 14:54 ` [PATCH 0/2] svcrdma: NFSRDMA Server fixes for 2.6.37 J. Bruce Fields
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=4CE4B923.6030102@opengridcomputing.com \
--to=tom@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=tom@ogc.us \
/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).