RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-31 11:08:11 +00:00
Code Issues Activity Actions

Kernel: Don't make a separate allocation for thread FPU state

Browse source 
We were allocating thread FPU state separately in order to ensure a
16-byte alignment. There should be no need to do that.

This patch makes it a regular value member of Thread instead, dodging
one heap allocation during thread creation.
This commit is contained in:
Andreas Kling 2021-08-05 22:29:38 +02:00
parent d5d8fba579
commit 584fa525eb
2 changed files with 7 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Kernel/Thread.h
View file

@ -1038,7 +1038,7 @@ public:
u32 pending_signals() const;
u32 pending_signals_for_state() const;
FPUState& fpu_state() { return *m_fpu_state; }
FPUState& fpu_state() { return m_fpu_state; }
KResult make_thread_specific_region(Badge<Process>);
@ -1215,7 +1215,7 @@ public:
String backtrace();
private:
Thread(NonnullRefPtr<Process>, NonnullOwnPtr<Region>, NonnullRefPtr<Timer>, NonnullOwnPtr<FPUState>, OwnPtr<KString>);
Thread(NonnullRefPtr<Process>, NonnullOwnPtr<Region>, NonnullRefPtr<Timer>, OwnPtr<KString>);
IntrusiveListNode<Thread> m_process_thread_list_node;
int m_runnable_priority { -1 };
@ -1344,7 +1344,7 @@ private:
unsigned m_ipv4_socket_read_bytes { 0 };
unsigned m_ipv4_socket_write_bytes { 0 };
OwnPtr<FPUState> m_fpu_state;
FPUState m_fpu_state {};
State m_state { Invalid };
OwnPtr<KString> m_name;
u32 m_priority { THREAD_PRIORITY_NORMAL };