From: David Mentre <David.Mentre@irisa.fr>
To: pmonta@imedia.com
Cc: steve@icarus.icarus.com, linux-kernel@vger.rutgers.edu,
torvalds@transmeta.com, linux-mm@,
@kvack.org
Subject: Re: bigphysarea in 2.2
Date: 11 Apr 1998 12:56:10 +0200 [thread overview]
Message-ID: <wd8iuogfwz9.fsf@parate.irisa.fr> (raw)
In-Reply-To: Peter Monta's message of "Fri, 10 Apr 1998 10:46:54 -0700"
Peter Monta <pmonta@halibut.imedia.com> writes:
> > Is it too late to ask that the bigphysarea patch be included in the
> > 2.1-and-soon-to-be-2.2 kernel?
>
> Seconded. Thanks for offering to maintain it.
With the new kernel memory manager, and if the defragmenting code which
is under development works, wouldn't it be more useful to use standard
kernel memory allocation. Static allocation like in bigphysarea is more
a work-around that a real solution.
Maybe we should ask the memory kernel hackers (Stephen, Ben, Rick,
Werner?) to support big allocations. I personally need 512 Kbytes
contiguous blocks for a direct-from/to-memory network card. A possible
problem is that those blocks should 512 Kbytes aligned (Argh!! !*%&@
hardware).
Is it doable with current code in 2.1 (due to feature freeze) ? On the
other side, I agree that at least a work-around like bigphysarea should
be included in 2.2. More and more PCI cards make direct access to memory
for big transfers.
Regards,
d.
--
David.Mentre@irisa.fr -- http://www.irisa.fr/prive/dmentre/
== GNU & Linux: Change _our_ world ==
next parent reply other threads:[~1998-04-11 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199804101746.KAA15720@halibut.imedia.com>
1998-04-11 10:56 ` David Mentre [this message]
[not found] ` <199804202157.WAA03987@dax.dcs.ed.ac.uk>
1998-04-21 6:44 ` David Mentre
1998-04-21 21:28 ` Stephen C. Tweedie
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=wd8iuogfwz9.fsf@parate.irisa.fr \
--to=david.mentre@irisa.fr \
--cc=linux-kernel@vger.rutgers.edu \
--cc=pmonta@imedia.com \
--cc=steve@icarus.icarus.com \
--cc=torvalds@transmeta.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