From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760539AbYFSRaR (ORCPT ); Thu, 19 Jun 2008 13:30:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755487AbYFSR3u (ORCPT ); Thu, 19 Jun 2008 13:29:50 -0400 Received: from 166-70-238-42.ip.xmission.com ([166.70.238.42]:38850 "EHLO ns1.utah-nac.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751471AbYFSR3t (ORCPT ); Thu, 19 Jun 2008 13:29:49 -0400 Message-ID: <2932.69.2.248.210.1213895519.squirrel@webmail.wolfmountaingroup.com> Date: Thu, 19 Jun 2008 11:11:59 -0600 (MDT) Subject: Question about sys_ind (Partition ID fields) From: jmerkey@wolfmountaingroup.com To: linux-kernel@vger.kernel.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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