From: jmerkey@wolfmountaingroup.com
To: linux-kernel@vger.kernel.org
Subject: Question about sys_ind (Partition ID fields)
Date: Thu, 19 Jun 2008 11:11:59 -0600 (MDT) [thread overview]
Message-ID: <2932.69.2.248.210.1213895519.squirrel@webmail.wolfmountaingroup.com> (raw)
Is there a reason why the sys_ind field (The partition ID) is not cached
in the hd_struct persistently? I noticed that after the initial
check_partition calls through check_part[]() read all this data and only
remember the starting sector and size of a given partition. Perhaps I am
missing something, and its stored somewhere else, but I have not located
it yet.
This seems somwhat wasteful since it requires the partition tables and/or
partitions to be re-read all the time instead of just remembering what
sys_ind was previously set. The argument that it is this way for
supporting dynamic rescanning doesn't seem to match up to the way its
implemented since you have to rescan anyway in most cases. It makes it
somewhat ackward whem you are instrumenting multi-partition storage
modules.
Jeff
next reply other threads:[~2008-06-19 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 17:11 jmerkey [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-19 17:11 jmerkey
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=2932.69.2.248.210.1213895519.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.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®