From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org,
Linux-ntfs@tiger.informatik.hu-berlin.de,
linux-ntfs-dev@lists.sourceforge.net,
linux-ntfs-announce@lists.sourceforge.net
Subject: Re: ANN: NTFS new release available (1.1.15)
Date: Fri, 25 May 2001 19:59:24 -0400 [thread overview]
Message-ID: <3B0EF1DC.CD0DF4D7@mandrakesoft.com> (raw)
In-Reply-To: <5.1.0.14.2.20010526000503.04716ec0@pop.cus.cam.ac.uk>
Anton Altaparmakov wrote:
> NTFS 1.1.15 - ChangeLog
> =======================
> - Support for more than 128kiB sized runlists (using vmalloc_32() instead
> of kmalloc()).
If you are running into kmalloc size limit, please consider some
alternative method of allocation.
Can you map it into the page cache, as Al Viro has done in recent
patches?
Can you break your allocation into an array of pages, obtained via
get_free_page?
If runlists are on-disk structures, can you look at bh->b_data instead
of keeping them in memory?
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-25 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 23:49 ANN: NTFS new release available (1.1.15) Anton Altaparmakov
2001-05-25 23:59 ` Jeff Garzik [this message]
2001-05-26 0:42 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2001-05-27 11:23 ` [Linux-ntfs] " Martin von Loewis
2001-05-27 11:45 ` Anton Altaparmakov
2001-05-27 12:53 ` Martin von Loewis
2001-05-28 5:36 ` Yuri Per
2001-05-28 11:10 ` Martin von Loewis
2001-05-28 12:01 ` Anton Altaparmakov
2001-05-28 13:08 ` Yuri Per
2001-05-28 14:49 ` Anton Altaparmakov
2001-05-29 0:50 ` Jeff V. Merkey
2001-05-29 8:18 ` Martin von Loewis
2001-05-29 16:42 ` Jeff V. Merkey
2001-05-27 22:37 ` Anton Altaparmakov
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=3B0EF1DC.CD0DF4D7@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Linux-ntfs@tiger.informatik.hu-berlin.de \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-announce@lists.sourceforge.net \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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