From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: intel-sgx-kernel-dev@lists.01.org, platform-driver-x86@vger.kernel.org
Subject: Re: [intel-sgx-kernel-dev] [PATCH RFC v3 07/12] intel_sgx: driver for Intel Software Guard Extensions
Date: Tue, 7 Nov 2017 20:47:09 +0200 [thread overview]
Message-ID: <20171107184709.srgrx2aa23fupmk7@linux.intel.com> (raw)
In-Reply-To: <8b91bb10-de7d-c0c1-6373-7a565625525f@intel.com>
On Mon, Nov 06, 2017 at 07:54:00AM -0800, Dave Hansen wrote:
> On 10/10/2017 07:32 AM, Jarkko Sakkinen wrote:
> > +static LIST_HEAD(sgx_free_list);
> > +static DEFINE_SPINLOCK(sgx_free_list_lock);
>
> Is this a global list? Will this be a scalability problem on larger
> systems?
It will be need to be refined for NUMA.
In addition, per-CPU caches would probably make sense.
For simplicity, I would keep it as it is up until the driver is in the
mainline.
/Jarkko
next prev parent reply other threads:[~2017-11-07 18:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:32 [PATCH RFC v3 00/12] Intel(R) SGX Driver Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 01/12] intel_sgx: updated MAINTAINERS Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 02/12] x86: add SGX definition to cpufeature Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 03/12] x86: define the feature control MSR's SGX enable bit Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 04/12] x86: define the feature control MSR's SGX launch control bit Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 05/12] x86: add SGX MSRs to msr-index.h Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 06/12] fs/pipe.c: export create_pipe_files() and replace_fd() Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 08/12] intel_sgx: ptrace() support Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 09/12] intel_sgx: driver documentation Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 10/12] intel_sgx: in-kernel launch enclave Jarkko Sakkinen
2017-11-08 20:07 ` [intel-sgx-kernel-dev] " Sean Christopherson
2017-11-14 14:22 ` Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 11/12] intel_sgx: glue code for in-kernel LE Jarkko Sakkinen
2017-10-10 14:32 ` [PATCH RFC v3 12/12] intel_sgx: update IA32_SGXLEPUBKEYHASH* MSRs Jarkko Sakkinen
[not found] ` <20171010143258.21623-8-jarkko.sakkinen@linux.intel.com>
2017-10-10 15:41 ` [intel-sgx-kernel-dev] [PATCH RFC v3 07/12] intel_sgx: driver for Intel Software Guard Extensions Sean Christopherson
2017-10-11 11:46 ` Jarkko Sakkinen
2017-10-11 15:56 ` Sean Christopherson
2017-10-10 18:26 ` Sean Christopherson
2017-10-13 19:58 ` Jarkko Sakkinen
2017-10-13 20:02 ` Jarkko Sakkinen
2017-10-13 20:08 ` Jarkko Sakkinen
2017-10-13 20:13 ` Jarkko Sakkinen
2017-10-12 16:48 ` Sean Christopherson
2017-10-13 19:16 ` Jarkko Sakkinen
2017-11-02 19:48 ` Sean Christopherson
2017-11-06 7:23 ` Jarkko Sakkinen
2017-11-02 20:10 ` Sean Christopherson
2017-11-06 11:08 ` Jarkko Sakkinen
2017-11-06 11:33 ` Jarkko Sakkinen
2017-11-06 14:56 ` Sean Christopherson
2017-11-08 6:25 ` Jarkko Sakkinen
2017-11-06 11:39 ` Jarkko Sakkinen
2017-11-06 14:54 ` Sean Christopherson
2017-11-07 18:43 ` Jarkko Sakkinen
2017-11-06 15:54 ` Dave Hansen
2017-11-07 18:47 ` Jarkko Sakkinen [this message]
2017-11-07 19:05 ` Dave Hansen
2017-11-14 19:33 ` Jarkko Sakkinen
2017-11-14 21:05 ` Jarkko Sakkinen
2017-11-14 21:12 ` Dave Hansen
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=20171107184709.srgrx2aa23fupmk7@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=intel-sgx-kernel-dev@lists.01.org \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.