From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Stefan Smietanowski <stesmi@stesmi.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [ANNOUNCE] libata: new EH, NCQ, hotplug and PM patches against stable kernel
Date: Sat, 13 May 2006 17:15:24 +0900 [thread overview]
Message-ID: <4465959C.8040906@gmail.com> (raw)
In-Reply-To: <44658C43.8090305@garzik.org>
Jeff Garzik wrote:
> Tejun Heo wrote:
>> Jeff Garzik wrote:
>>> Tejun Heo wrote:
>>>> Stefan Smietanowski wrote:
>>>>> Randy.Dunlap wrote:
>>>>>>> * New error handling
>>>>>>> * IRQ driven PIO (from Albert Lee)
>>>>>>> * SATA NCQ support
>>>>>>> * Hotplug support
>>>>>>> * Port Multiplier support
>>>>>>
>>>>>> BTW, we often use PM to mean Power Management.
>>>>>> Could we find a different acronym for Port Multiplier support,
>>>>>> such as PMS or PX or PXS?
>>>>>
>>>>> Ok, maybe not PMS ?
>>>>>
>>>>> Can you imagine a bug report from someone that "has problem with PMS"?
>>>>> :)
>>>>>
>>>>
>>>> Would be fun though. :)
>>>>
>>>> I thought about using another acronym for port multiplier too. But
>>>> the spec uses that acronym all over the place, PM, PMP (Port
>>>> Multiplier Portnumber), which reminds me of USB full/high speed fiasco.
>>>>
>>>> Urghh... I thought we could use power for power management inside
>>>> libata but that might be a bad idea. So, PMS?
>>>
>>> PMS is fine. I encouraged the use of "UFO" for "UDP Fragmentation
>>> Offload" in network driver land, and it stuck.
>>>
>>> This is Linux, we like to have fun around here :)
>>>
>>
>> Currently, the candidates are...
>>
>> px : short (good), but I don't know, not pretty
>> pmul : okay but a bit too long
>> pml : pretty and official
>> pms : pretty and fun
>>
>> I think I'll go with either pms or pml. Man, this decision is difficult.
>
> To make it more difficult: Honestly, I prefer Port MultiPlier (PMP),
> imitating (and perhaps overloading) the acronym used by the standard
> SATA FIS field.
Ah... I've excluded PMP because I thought it was already taken, but,
yeah, it wouldn't cause noticeable confusion and fits the best. I'll
give PMP a try.
--
tejun
next prev parent reply other threads:[~2006-05-13 8:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 13:24 [ANNOUNCE] libata: new EH, NCQ, hotplug and PM patches against stable kernel Tejun Heo
2006-05-12 19:21 ` Randy.Dunlap
2006-05-12 19:22 ` Stefan Smietanowski
2006-05-12 22:02 ` Tejun Heo
2006-05-13 0:20 ` Stefan Smietanowski
2006-05-13 1:38 ` Matthew Frost
2006-05-13 4:13 ` Jeff Garzik
2006-05-13 7:29 ` Tejun Heo
2006-05-13 7:35 ` Jeff Garzik
2006-05-13 8:15 ` Tejun Heo [this message]
2006-05-15 14:25 ` Alan Cox
2006-05-15 16:53 ` Stefan Smietanowski
2006-05-16 14:42 ` Michael Schierl
2006-05-16 14:59 ` Jeff Garzik
2006-05-16 15:14 ` Michael Schierl
2006-05-17 1:28 ` zhao, forrest
2006-05-17 12:48 ` AHCI suspend works for me! (was: [ANNOUNCE] libata: new EH, NCQ, hotplug and PM patches against stable kernel) Michael Schierl
2006-05-18 15:27 ` [ANNOUNCE] libata: new EH, NCQ, hotplug and PM patches against stable kernel Jeff Garzik
2006-06-21 21:18 ` Nicolas STRANSKY
2006-06-22 7:21 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 15:34 Mikael Pettersson
2006-05-12 23:10 ` Tejun Heo
2006-05-13 4:12 ` Jeff Garzik
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=4465959C.8040906@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stesmi@stesmi.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;
as well as URLs for NNTP newsgroup(s).