All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Martin Wilck <mwilck@suse.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Bart Van Assche <Bart.VanAssche@wdc.com>,
	"hch@infradead.org" <hch@infradead.org>,
	"viswas.g@microsemi.com" <viswas.g@microsemi.com>,
	"gerry.morong@microsemi.com" <gerry.morong@microsemi.com>,
	"mahesh.rajashekhara@microsemi.com"
	<mahesh.rajashekhara@microsemi.com>,
	"POSWALD@suse.com" <POSWALD@suse.com>,
	"scott.benesh@microsemi.com" <scott.benesh@microsemi.com>,
	"don.brace@microsemi.com" <don.brace@microsemi.com>,
	"bader.alisaleh@microsemi.com" <bader.alisaleh@microsemi.com>,
	"kevin.barnett@microsemi.com" <kevin.barnett@microsemi.com>,
	"joseph.szczypek@hpe.com" <joseph.szczypek@hpe.com>,
	"scott.teel@microsemi.com" <scott.teel@microsemi.com>,
	"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	justin.li
Subject: Re: [PATCH] sd: preserve sysfs updates to max_sectors_kb
Date: Wed, 27 Sep 2017 21:37:37 -0400	[thread overview]
Message-ID: <yq1bmlva9i6.fsf@oracle.com> (raw)
In-Reply-To: <1504953142.5442.1.camel@suse.com> (Martin Wilck's message of "Sat, 09 Sep 2017 12:32:22 +0200")


Martin,

> Could you please explain why you think Don's patch is wrong? User
> settings being discarded because of a BLKRRPART ioctl violates the
> principle of least surprise. With Don's patch, that won't happen any
> more. If hardware limits change, whether they increase or decrease, the
> patch will also do the Right Thing, AFAICS. Increasing hw limits will
> not automatically increase the sw limit, but IMO that's actually
> expected.

I have been mulling over this for a while.

I suggest the following...

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2017-09-28  1:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 21:00 [PATCH] sd: preserve sysfs updates to max_sectors_kb Don Brace
2017-08-18 21:05 ` Bart Van Assche
2017-08-18 21:29   ` Don Brace
2017-08-18 21:46     ` Bart Van Assche
2017-08-21 19:12       ` Don Brace
2017-08-21 19:53         ` Bart Van Assche
2017-08-21 20:14           ` Don Brace
2017-08-29 17:41             ` Don Brace
2017-08-29 17:42             ` Don Brace
2017-08-29 18:13               ` Bart Van Assche
2017-08-29 18:36                 ` Don Brace
2017-08-29 19:41                   ` Don Brace
2017-08-29 22:25                     ` Bart Van Assche
2017-08-29 22:32                       ` Don Brace
2017-08-29 23:00                         ` Bart Van Assche
2017-08-30  1:24                           ` Martin K. Petersen
2017-09-09 10:32                             ` Martin Wilck
2017-09-28  1:37                               ` Martin K. Petersen [this message]
2017-09-28  1:38 ` [PATCH] scsi: sd: Do not override max_sectors_kb sysfs setting Martin K. Petersen
2017-09-29 12:26   ` Martin Wilck
2017-09-29 13:46   ` Don Brace

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=yq1bmlva9i6.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=POSWALD@suse.com \
    --cc=bader.alisaleh@microsemi.com \
    --cc=don.brace@microsemi.com \
    --cc=gerry.morong@microsemi.com \
    --cc=hch@infradead.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=joseph.szczypek@hpe.com \
    --cc=kevin.barnett@microsemi.com \
    --cc=mahesh.rajashekhara@microsemi.com \
    --cc=mwilck@suse.com \
    --cc=scott.benesh@microsemi.com \
    --cc=scott.teel@microsemi.com \
    --cc=viswas.g@microsemi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.