From: Christoph Hellwig <hch@infradead.org>
To: Olivier Galibert <galibert@pobox.com>,
"Hack inc." <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: Can a non-sg scsi write command be more than PAGE_SIZE length?
Date: Tue, 19 Apr 2005 10:29:26 +0100 [thread overview]
Message-ID: <20050419092926.GA9785@infradead.org> (raw)
In-Reply-To: <20050419092431.GA98975@dspnet.fr.eu.org>
On Tue, Apr 19, 2005 at 11:24:31AM +0200, Olivier Galibert wrote:
> > Yes, it's allowed.
>
> Thanks. Pages in that case are continuous then, right?
Good question actually. I know XFS does passed vmalloc'ed memory down
the block I/O path, but that's as a scatter/gather request. All non-s/g
request should be contingous I think.
We really need to write down the rules about what memory can be passed
down the block I/O path - XFS for example sends kmalloced memory down
which all the iSCSI implementations don't like at all.
next parent reply other threads:[~2005-04-19 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050419084730.GA96767@dspnet.fr.eu.org>
[not found] ` <20050419085008.GA9194@infradead.org>
[not found] ` <20050419092431.GA98975@dspnet.fr.eu.org>
2005-04-19 9:29 ` Christoph Hellwig [this message]
2005-04-19 14:14 ` Can a non-sg scsi write command be more than PAGE_SIZE length? James Bottomley
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=20050419092926.GA9785@infradead.org \
--to=hch@infradead.org \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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