From: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Hiroshi.DOYU@nokia.com" <Hiroshi.DOYU@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scatterlist: define SG chain for arm architecture
Date: Fri, 1 Oct 2010 13:54:37 -0500 [thread overview]
Message-ID: <496565EC904933469F292DDA3F1663E602F46545F2@dlee06.ent.ti.com> (raw)
In-Reply-To: <20101001163958.GA22533@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk]
> Sent: Friday, October 01, 2010 11:40 AM
> To: Guzman Lugo, Fernando
> Cc: linux-arm-kernel@lists.infradead.org;
> Hiroshi.DOYU@nokia.com; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] scatterlist: define SG chain for arm architecture
>
> On Fri, Oct 01, 2010 at 11:28:41AM -0500, Fernando Guzman Lugo wrote:
> > Define SG chain for ARM architecture in order to work with big
> > buffers. This patch is needed in order to iovmm users can
> pass a big
> > buffer to map it and ARM architecture has not issues using SG chain.
> >
> > This change was suggested by FUJITA Tomonori.
>
> Have you audited all places where SG lists are used in the
> ARM architecture to ensure that SG chain support is safe?
> (That goes for ARM generic code and ARM specific drivers.)
Unfortunately I only can test on omap platform. I am not so
Familiar with scatter gather code and what is the restriction
For one page size of SG list (maybe they can comment). However
For SG chaining seems there is no restriction with the exception
Of using the with function to assigned to page and iterate each
Element of the list and it has sometime when SG chaining was
Introduce all the code should be use this new functions.
I am agree with you about make sure nothing is broken with the change.
Maybe some people of other arm platforms can comment if they have
Issues with the patch and test the change and if there is no complain
Then merge the change. If there are issues maybe I can send the patch
Just for omap platform. However, looks like there is no issues enabling
It to all arm, but again I am not so familiar with SG, so I will let
The experts to comment.
Thanks a lot,
Fernando.
>
> If the answer is no, this patch is unacceptable until such a
> review has been carried out.
>
next prev parent reply other threads:[~2010-10-01 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 16:28 Fernando Guzman Lugo
2010-10-01 16:39 ` Russell King - ARM Linux
2010-10-01 18:54 ` Guzman Lugo, Fernando [this message]
2010-10-03 11:02 ` FUJITA Tomonori
2010-10-03 11:28 ` Russell King - ARM Linux
2010-10-03 11:34 ` FUJITA Tomonori
2010-12-02 17:41 ` Guzman Lugo, Fernando
2010-12-06 19:23 ` Guzman Lugo, Fernando
-- strict thread matches above, loose matches on Subject: below --
2010-10-01 3:22 Fernando Guzman Lugo
2010-10-01 3:50 ` Guzman Lugo, Fernando
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=496565EC904933469F292DDA3F1663E602F46545F2@dlee06.ent.ti.com \
--to=fernando.lugo@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®