From: David Serrano <dserrano5@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Tiny reordering of some fields of task_struct
Date: Thu, 28 Apr 2005 22:17:02 +0200 [thread overview]
Message-ID: <20050428201702.GA1992@genus.hue-bond.info> (raw)
(First post & first patch so please be kind O:))
Playing with some things (I'm just beginning with this whole kernel stuff) I
found that there are three filesystem-related members in task_struct that
aren't together:
/* file system info */
int link_count, total_link_count;
/* ipc stuff */
struct sysv_sem sysvsem;
/* CPU-specific state of this task */
struct thread_struct thread;
/* filesystem information */
struct fs_struct *fs;
[...]
/* journalling filesystem info */
void *journal_info;
Perhaps there is some reason to have them as they are now but if that's not
the case, this joins them together. It's against 2.6.12-rc3.
Signed-off-by: David Serrano <dserrano5@gmail.com>
--- linux-2.6.12-rc3/include/linux/sched.h.orig 2005-04-28 22:05:05.000000000 +0200
+++ linux-2.6.12-rc3/include/linux/sched.h 2005-04-28 22:05:07.000000000 +0200
@@ -616,14 +616,14 @@ struct task_struct {
#endif
int oomkilladj; /* OOM kill score adjustment (bit shift). */
char comm[TASK_COMM_LEN];
-/* file system info */
+/* filesystem information */
int link_count, total_link_count;
+ struct fs_struct *fs;
+ void *journal_info;
/* ipc stuff */
struct sysv_sem sysvsem;
/* CPU-specific state of this task */
struct thread_struct thread;
-/* filesystem information */
- struct fs_struct *fs;
/* open file information */
struct files_struct *files;
/* namespace */
@@ -654,9 +654,6 @@ struct task_struct {
/* context-switch lock */
spinlock_t switch_lock;
-/* journalling filesystem info */
- void *journal_info;
-
/* VM state */
struct reclaim_state *reclaim_state;
--
David Serrano
reply other threads:[~2005-04-28 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050428201702.GA1992@genus.hue-bond.info \
--to=dserrano5@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®