DPDK patches and discussions
 help / color / mirror / Atom feed
From: "David Harton (dharton)" <dharton@cisco.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Retire x86 32 bit?
Date: Tue, 17 Apr 2018 18:39:26 +0000	[thread overview]
Message-ID: <9315b1fd275c48508640f4553be62d0b@XCH-RCD-016.cisco.com> (raw)
In-Reply-To: <CAOaVG152U3TTCHC5h88T0y-SN+=A9Yn55AhOPnueYWg8KF=Svg@mail.gmail.com>

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)?

  reply	other threads:[~2018-04-17 18:39 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) [this message]
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
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=9315b1fd275c48508640f4553be62d0b@XCH-RCD-016.cisco.com \
    --to=dharton@cisco.com \
    --cc=dev@dpdk.org \
    --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).