From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: A question about terminology.
Date: Fri, 23 Jan 2004 08:21:45 +1300 [thread overview]
Message-ID: <1074799304.12771.93.camel@laptop-linux> (raw)
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
Hi again.
When I began work on swapfile support, I looked for an efficient method
to store all the information on which blocks were used. The process led
me to develop something I called ranges, which Pavel later looked at and
said something like 'Oh. Extents.'
Throughout the code, I still call them ranges (I have, for example
struct range and struct rangechain). In preparation for merging, should
I go through an rename ranges to extents, or will they be okay as it is?
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-01-22 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 19:21 Nigel Cunningham [this message]
2004-01-23 6:27 ` A question about terminology Andrew Morton
2004-01-23 7:20 ` Nigel Cunningham
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=1074799304.12771.93.camel@laptop-linux \
--to=ncunningham@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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