From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com, viro@math.psu.edu
Subject: kill i_dev
Date: Thu, 21 Nov 2002 01:07:25 +0100 (MET) [thread overview]
Message-ID: <UTC200211210007.gAL07Pa07926.aeb@smtp.cwi.nl> (raw)
One disadvantage of enlarging the size of dev_t is
that struct inode grows. Bad.
We used to have i_dev and i_rdev; today i_rdev has split into
i_rdev, i_bdev and i_cdev. Bad.
It looks like these four fields can be replaced by a single one,
making struct inode smaller. Not bad.
The first step would be to delete the field i_dev, and
all assignments to it, and replace all remaining occurrences
by i_sb->s_dev.
Roughly speaking, the only use of this field is in the stat
system call.
Any objections?
Andries
next reply other threads:[~2002-11-21 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 0:07 Andries.Brouwer [this message]
2002-11-21 0:39 ` Alexander Viro
2002-11-21 1:33 Andries.Brouwer
2002-11-21 2:58 ` Alexander Viro
2002-11-21 18:12 Andries.Brouwer
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=UTC200211210007.gAL07Pa07926.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®