From: Jens Axboe <axboe@suse.de>
To: mdaljeet@in.ibm.com
Cc: Gerd Knorr <kraxel@bytesex.org>, linux-kernel@vger.kernel.org
Subject: Re: mmap
Date: Tue, 3 Jul 2001 19:47:16 +0200 [thread overview]
Message-ID: <20010703194716.A1027@suse.de> (raw)
In-Reply-To: <CA256A7D.004D2B0F.00@d73mta01.au.ibm.com>
In-Reply-To: <CA256A7D.004D2B0F.00@d73mta01.au.ibm.com>
On Mon, Jul 02 2001, mdaljeet@in.ibm.com wrote:
> [1] IMHO it would be more useful if iobufs would use a scatterlist
> instead of an struct page* array.
No that would be horrible, at least with the current scatterlist. A page
based scatterlist would be alright though -- but this boils down to the
per-page offset debate again.
--
Jens Axboe
next prev parent reply other threads:[~2001-07-03 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 14:00 mmap mdaljeet
2001-07-03 17:47 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-02 12:20 mmap Sébastien Paumier
2011-12-02 14:45 ` mmap Eric Dumazet
2001-05-15 10:08 mmap mdaljeet
2001-05-15 6:47 mmap mdaljeet
2001-05-15 7:33 ` mmap Gerd Knorr
2001-05-15 9:42 ` mmap Alan Cox
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=20010703194716.A1027@suse.de \
--to=axboe@suse.de \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdaljeet@in.ibm.com \
/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).