From: Caspar Zhang <czhang@redhat.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] ksm: mempolicy syscalls not implemented
Date: Fri, 15 Apr 2011 23:32:20 +0800 [thread overview]
Message-ID: <4DA86504.4070703@redhat.com> (raw)
In-Reply-To: <a8c42cda82df15baf9acaf89ed09b41cc8cb5af8.1302595961.git.czhang@redhat.com>
On 04/12/2011 04:13 PM, Caspar Zhang wrote:
>
> since NUMA is only supported on a few i386 systems, mempolicy syscalls
> ([gs]et_mempolicy, mbind) may not implemented, thus, an ENOSYS errno
> should be acceptable.
>
> Signed-off-by: Caspar Zhang <czhang@redhat.com>
> ---
> testcases/kernel/mem/ksm/ksm02.c | 9 +++++++--
> testcases/kernel/mem/ksm/ksm04.c | 9 +++++++--
> 2 files changed, 14 insertions(+), 4 deletions(-)
>
Hi, anyone can review this patch and get it merged if suitable?
Thanks,
Caspar
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2011-04-15 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4ad73abd0251782d607e88f90a4a1a26001d9ea.1302595961.git.czhang@redhat.com>
2011-04-12 8:13 ` [LTP] [PATCH] ksm: mempolicy syscalls not implemented Caspar Zhang
2011-04-15 15:32 ` Caspar Zhang [this message]
2011-04-19 16:27 ` Cyril Hrubis
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=4DA86504.4070703@redhat.com \
--to=czhang@redhat.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