From: Phillip Susi <psusi@cfl.rr.com>
To: Peter Osterlund <petero2@telia.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: [PATCH] pktcdvd & udf bugfixes
Date: Sun, 15 Jan 2006 17:27:00 -0500 [thread overview]
Message-ID: <43CACC34.504@cfl.rr.com> (raw)
In-Reply-To: <m3k6d1z87g.fsf@telia.com>
Surely the kernel can allocate pagable memory if it chooses to? I think
in the case of pktcdvd it would be best for the buffers to be pagable
when initially allocated and filled, and only locked into memory when
the bio is sent down to the cdrom driver. That way you could keep a
fairly large number of buffers on larger ( 256 KB+ ) packets in memory
for write combining, without placing undue burden on non paged pool.
Peter Osterlund wrote:
>>Ahh, excellent. Also, is the memory currently non pagable? Is there
>>a reason for that?
>>
>>
>
>Yes the memory is non pagable. The linux kernel doesn't support
>pagable kernel memory, only user space memory can be swapped out.
>
>
>
next prev parent reply other threads:[~2006-01-15 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 4:12 [PATCH] pktcdvd & udf bugfixes Phillip Susi
2006-01-12 9:02 ` Pekka Enberg
2006-01-14 14:08 ` Peter Osterlund
2006-01-14 18:35 ` Phillip Susi
2006-01-14 21:45 ` Peter Osterlund
2006-01-14 23:01 ` Phillip Susi
2006-01-15 17:24 ` Peter Osterlund
2006-01-15 17:43 ` Phillip Susi
2006-01-15 17:56 ` Peter Osterlund
2006-01-15 22:27 ` Phillip Susi [this message]
2006-01-15 23:03 ` Peter Osterlund
2006-01-15 22:48 ` Peter Osterlund
2006-01-16 3:01 ` Phillip Susi
2006-01-16 6:49 ` Peter Osterlund
2006-01-19 20:46 ` Phillip Susi
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=43CACC34.504@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.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