From: "Seth, Rohit" <rohit.seth@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Linux IA64 ToDo List
Date: Sat, 23 Feb 2002 02:02:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905183@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905170@msgid-missing>
Don,
Currently working on the following:
1- NAT page support
2- Large Page support (for shared memory and anonymous pages).
3- Mckinley specific optimizations in Kernel memory related functions
(clear_page, copy_page, memset, memcp, TCP checksum)
rohit
-----Original Message-----
From: n0ano@indstorage.com [mailto:n0ano@indstorage.com]
Sent: Friday, February 22, 2002 8:57 AM
To: linux-ia64@linuxia64.org
Subject: [Linux-ia64] Linux IA64 ToDo List
It's been brought to my attention that the Linux IA64 ToDo list
has gotten rather out of date. I'm willing to fix this and
keep the list up to date but I need help from everyone else.
I need to know what people are doing. (I also need to know what
you're not doing :-)
What I'm looking for is both what you are actively working on
and also what you would like to see done. If you could send
me a simple email about this I'll collate everything and put
it up on the ToDo list at `www.linuxia64.org/todo.html'.
I'll start it off. I have two tasks I'm working on right now.
1. Remove race from IA32 `mmap' system call.
2. Fix coredump when OpenOffice/ia32 saves a spreadsheet as
a StarCalc 6.0 file.
Anyone else?
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2002-02-23 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 16:57 [Linux-ia64] Linux IA64 ToDo List n0ano
2002-02-22 18:49 ` David Mosberger
2002-02-22 19:06 ` Luck, Tony
2002-02-23 2:02 ` Seth, Rohit [this message]
2002-02-23 2:32 ` Jim Wilson
2002-02-25 6:04 ` Don Dugger
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=marc-linux-ia64-105590701905183@msgid-missing \
--to=rohit.seth@intel.com \
--cc=linux-ia64@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