From: Peter Osterlund <petero2@telia.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: [PATCH] pktcdvd & udf bugfixes
Date: 15 Jan 2006 18:56:03 +0100 [thread overview]
Message-ID: <m3k6d1z87g.fsf@telia.com> (raw)
In-Reply-To: <43CA89A4.3010000@cfl.rr.com>
Phillip Susi <psusi@cfl.rr.com> writes:
> Peter Osterlund wrote:
>
> >Phillip Susi <psusi@cfl.rr.com> writes:
> >
> >>Peter Osterlund wrote:
> >> > OK, so it appears you can make packets bigger than 64KB. Can I please
> >>
> >>>have those patches so I can test this myself.
> >>>
> >>Sure, patches attached.
> >>
> >>patch-6 is the one you are interested in for the different sizes
> >
> >Thanks, it seems to work just fine. I have put the overflow and zero
> >check changes in my kernel patch queue.
> >
> >However, I want to wait with the increased max packet size until the
> >memory allocation strategy has been changed to avoid wasting lots of
> >memory in the common cases. I will go work on a patch to do that now.
> >
> 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.
--
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340
next prev parent reply other threads:[~2006-01-15 17:56 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 [this message]
2006-01-15 22:27 ` Phillip Susi
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=m3k6d1z87g.fsf@telia.com \
--to=petero2@telia.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.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