From: Jim Murphy <jmurphy@arista.com>
To: Roger B Melton <rmelton@cisco.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"David Harton (dharton)" <dharton@cisco.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Retire x86 32 bit?
Date: Wed, 18 Apr 2018 10:40:37 -0700 [thread overview]
Message-ID: <CAJC5fi232FQEvFy=DrzCkP90_TRiUQR1vE=cZXYPpwxNUC451g@mail.gmail.com> (raw)
In-Reply-To: <7d058c65-b14e-037a-e08c-199183d7c1a4@cisco.com>
Same for our case.
On Tue, Apr 17, 2018 at 2:18 PM, Roger B Melton <rmelton@cisco.com> wrote:
> On 4/17/18 4:46 PM, Stephen Hemminger wrote:
>
>> On Tue, 17 Apr 2018 13:01:14 -0700
>> Jim Murphy <jmurphy@arista.com> wrote:
>>
>> Still used in certain memory constrained environments.
>>>
>>>
>>> On Tue, Apr 17, 2018 at 11:39 AM, David Harton (dharton) <
>>> dharton@cisco.com>
>>> wrote:
>>>
>>> It is used and tested in production and non-production environments.
>>>>
>>>> Regards,
>>>> Dave
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: dev <dev-bounces@dpdk.org> On Behalf Of Stephen Hemminger
>>>>> Sent: Tuesday, April 17, 2018 2:31 PM
>>>>> To: dev@dpdk.org
>>>>> Subject: [dpdk-dev] Retire x86 32 bit?
>>>>>
>>>>> I wonder if x86 32 bit is still useful?
>>>>> Many distributions no longer support it, and not sure if it is tested
>>>>> througly by anyone.
>>>>>
>>>>> Maybe time to deprecate it (gradually)?
>>>>>
>>>>
>>>>
>>> Pure 32 bit, or x86-64 instructions and registers used in 32 bit mode
>> (which can be faster).
>> .
>>
>>
> Pure 32bit in our case. We do not use x32 ABI.
>
> -Roger
>
>
>
next prev parent reply other threads:[~2018-04-18 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 18:31 Stephen Hemminger
2018-04-17 18:39 ` David Harton (dharton)
2018-04-17 20:01 ` Jim Murphy
2018-04-17 20:46 ` Stephen Hemminger
2018-04-17 21:18 ` Roger B Melton
2018-04-18 17:40 ` Jim Murphy [this message]
2018-04-17 20:40 ` Bruce Richardson
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='CAJC5fi232FQEvFy=DrzCkP90_TRiUQR1vE=cZXYPpwxNUC451g@mail.gmail.com' \
--to=jmurphy@arista.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.com \
--cc=rmelton@cisco.com \
--cc=stephen@networkplumber.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).