From: Russell King <rmk@arm.linux.org.uk>
To: Fajun Chen <fajunchen@gmail.com>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org, akpm@osdl.org
Subject: Re: Bugs on Linux 2.6.18-rc2 sg code?
Date: Sun, 20 Aug 2006 10:01:10 +0100 [thread overview]
Message-ID: <20060820090110.GA18927@flint.arm.linux.org.uk> (raw)
In-Reply-To: <8202f4270608200051p688f4654ub6aecb604e0152f1@mail.gmail.com>
On Sun, Aug 20, 2006 at 01:51:33AM -0600, Fajun Chen wrote:
> I've tested mmap code in both 2.6.15.4 and 2.6.18-rc2 with
> sg_vma_nopage() from 2.6.15.4, this particular sg mmap bug seems to be
> fixed?$B!%!!#S#i#n#c#e!!#y#o#u#r!!#p#a#t#c#h!!#f#o#r!!#2!%#6!%#1#8!]#r#c#4!!#i#s!!essentially not different
This is unreadable...
> from 2.6.15.4 (the only difference is sg->offset, which is always 0
> for sg mmap or indirect IO), this should fix the problem. I'll test
> your patch next week to confirm it anyway.
>
> I would like to also report a potential cache coherency issue on sg
> when running on some processors other than i386. I ran into cache
> coherency issue on ARM XScale Iop80321.
I no longer touch SCSI, partly because the only SCSI based systems I
have are extremely (10 years) old now. All my SCSI knowledge is based
on ancient 2.4 code and is no longer relevant.
> Existing sg code for direct IO:
I don't think direct-IO has ever been tested and debugged on ARM either.
I wouldn't know where to start with direct-IO - never used and never
looked at it.
And more importantly (for me), I'd rather not get into another squabble
with James over cache coherency ideas, so I want to stay well away from
cache coherency and block devices, thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-08-20 9:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 1:43 Bugs on Linux 2.6.18-rc2 sg code? Fajun Chen
2006-08-18 22:00 ` Douglas Gilbert
2006-08-19 4:11 ` Douglas Gilbert
2006-08-19 17:20 ` Matthew Wilcox
2006-08-19 17:36 ` Douglas Gilbert
2006-08-19 17:41 ` Andrew Morton
2006-08-19 20:23 ` Matthew Wilcox
2006-08-20 1:00 ` Douglas Gilbert
2006-08-20 10:07 ` Arjan van de Ven
2006-08-20 17:47 ` Andrew Morton
2006-08-30 16:29 ` Fajun Chen
2006-08-19 18:55 ` James Bottomley
2006-08-20 1:36 ` Douglas Gilbert
[not found] ` <8202f4270608200051p688f4654ub6aecb604e0152f1@mail.gmail.com>
2006-08-20 9:01 ` Russell King [this message]
2006-08-28 21:12 ` Fajun Chen
2006-08-28 22:11 ` Douglas Gilbert
2006-08-21 21:07 ` Fajun Chen
2006-08-22 2:47 ` Douglas Gilbert
2006-08-22 4:27 ` Fajun Chen
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=20060820090110.GA18927@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=dougg@torque.net \
--cc=fajunchen@gmail.com \
--cc=linux-scsi@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).