public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerome Marchand <jmarchan@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk
Subject: Re: [Patch 7/8] Enhanced partition statistics: procfs
Date: Thu, 13 Dec 2007 19:29:37 +0100	[thread overview]
Message-ID: <47617A11.80502@redhat.com> (raw)
In-Reply-To: <20071213094744.eaa0b232.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Thu, 13 Dec 2007 18:36:45 +0100 Jerome Marchand wrote:
> 
>> Randy Dunlap wrote:
>>> The format of the /proc file is not changed except to add data
>>> at the end of each line.  Is that correct?
>>>
>> No. The line concerning partitions will display different data. The new format match the current format
>> concerning disks.
>>
>> Current partition format:
>> major minor name reads_issued sectors_read writes_issued sectors_written
>>
>> New partition format (current disk format):
>> major minor name reads_issued reads_merged sector_read ms_reading writes_completed writes_merged sectors_written ms_writing I/Os_running ms_I/O weighted_ms_I/O
> 
> 
> I would have expected the /proc file contents to represent a user
> interface that we shouldn't change, other than by adding to the end
> of each line.
> 

I could eventually keep the old data and add the new ones at the end
of the line, but it will leads to a less coherent interface. Moreover
all the users of /proc/diskstats I know about use the number of field
to make the distinction between current disk and partitions
format. They all will be confused if we add new fields.

Jérôme


      reply	other threads:[~2007-12-13 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 16:18 [Patch 7/8] Enhanced partition statistics: procfs Jerome Marchand
2007-12-13 17:07 ` Randy Dunlap
2007-12-13 17:36   ` Jerome Marchand
2007-12-13 17:47     ` Randy Dunlap
2007-12-13 18:29       ` Jerome Marchand [this message]

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=47617A11.80502@redhat.com \
    --to=jmarchan@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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