From: Caspar Zhang <caspar@casparzhang.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: [LTP] hugemmap02/03?
Date: Wed, 29 Aug 2012 17:34:02 +0800 [thread overview]
Message-ID: <503DE20A.8010200@casparzhang.com> (raw)
I looked into hugemmap02 and hugemmap03, they were about huge maping in
high region/low region. After checked the codes, I don't think they're
well-implmented, or even worse, I don't think the tests make too much
sense. I don't know mmap regions very well, is there any other comments
against these two cases?
Caspar
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2012-08-29 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 9:34 Caspar Zhang [this message]
2012-10-03 9:55 ` [LTP] hugemmap02/03? chrubis
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=503DE20A.8010200@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@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