linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Domke <jens.domke@riken.jp>
To: Leon Romanovsky <leon@kernel.org>, Haim Boozaglo <haimbo@mellanox.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: "ibstat -l" displays CA device list in an unsorted order
Date: Wed, 26 Feb 2020 02:18:06 +0900	[thread overview]
Message-ID: <52f4364b-30c5-5c62-36bb-78341ca8fe6e@riken.jp> (raw)
In-Reply-To: <20200225091815.GE5347@unreal>

Dear Leon,

with all due respect, but if you don't want to be part of the solution,
then please at least stop being part of the problem!

I (and highly likely many other admins out there who don't follow this
list) am in full support of Haim's request for sorted output.

Not everything can/will be pinned down in a manpage, but if you insist
then sure someone can submit a amendment to the ibstat documentation
which demands alphanumeric sorting for the NICs/ports.

Best,
Jens


On 2/25/20 6:18 PM, Leon Romanovsky wrote:
> On Tue, Feb 25, 2020 at 10:36:05AM +0200, Haim Boozaglo wrote:
>>
>>
>> On 2/25/2020 9:48 AM, Leon Romanovsky wrote:
>>> On Mon, Feb 24, 2020 at 08:06:56PM +0200, Haim Boozaglo wrote:
>>>> Hi all,
>>>>
>>>> When running "ibstat" or "ibstat -l", the output of CA device list
>>>> is displayed in an unsorted order.
>>>>
>>>> Before pull request #561, ibstat displayed the CA device list sorted in
>>>> alphabetical order.
>>>>
>>>> The problem is that users expect to have the output sorted in alphabetical
>>>> order and now they get it not as expected (in an unsorted order).
>>>
>>> Do we have anything written in official man pages about this expectation?
>>> I don't think so, there is nothing "to fix".
>>>
>>> Thanks
>>>
>>>>
>>>> Best Regards,
>>>> Haim Boozaglo.
>>
>> Ok, but for many years people got used to getting sorted output in
>> alphabetical order and now they don't get it.
> 
> Like for many other things, those people will adapt.
> 
> Thanks
> 

  reply	other threads:[~2020-02-25 17:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 18:06 "ibstat -l" displays CA device list in an unsorted order Haim Boozaglo
2020-02-24 19:41 ` Jason Gunthorpe
2020-02-25  8:25   ` Haim Boozaglo
2020-02-26 13:43     ` Jason Gunthorpe
2020-02-26 13:57       ` Leon Romanovsky
2020-02-26 17:09         ` Jason Gunthorpe
2020-02-27  7:48           ` Haim Boozaglo
2020-02-27 12:49             ` Leon Romanovsky
2020-02-27 12:57               ` Vladimir Koushnir
2020-02-27 13:59                 ` Leon Romanovsky
2020-02-27 13:33             ` Jason Gunthorpe
2020-02-27 14:55               ` Dennis Dalessandro
2020-02-27 15:26                 ` Jason Gunthorpe
2020-02-25  7:48 ` Leon Romanovsky
2020-02-25  8:36   ` Haim Boozaglo
2020-02-25  9:18     ` Leon Romanovsky
2020-02-25 17:18       ` Jens Domke [this message]
2020-02-25 19:43         ` Leon Romanovsky
2020-02-26 13:42           ` Dennis Dalessandro
2020-02-26 13:56             ` Leon Romanovsky

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=52f4364b-30c5-5c62-36bb-78341ca8fe6e@riken.jp \
    --to=jens.domke@riken.jp \
    --cc=haimbo@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).