From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH v2 0/2] Fix file locking in EAL memory
Date: Tue, 24 Apr 2018 22:05:10 +0200 [thread overview]
Message-ID: <2542114.cvfhNbjQKQ@xps> (raw)
In-Reply-To: <3898cc9f-f41f-de8e-a89f-f8f35c7444e8@intel.com>
24/04/2018 19:25, Burakov, Anatoly:
> On 24-Apr-18 5:32 PM, Stephen Hemminger wrote:
> > On Tue, 24 Apr 2018 16:54:21 +0100
> > Anatoly Burakov <anatoly.burakov@intel.com> wrote:
> >
> >> One of the ways to work around this was using OFD locks,
> >> but they are only supported on kernels 3.15+,
> >
> > Maybe time to move to next LTS kernel (3.16)?
> >
>
> I'm all for it, but it's not my call to make :(
I am in favor of upgrading kernel requirements.
The discussion already started few months ago:
https://dpdk.org/patch/34778
We just need to consider how to support the latest versions
of distributions Debian, Ubuntu, SLES and RHEL.
next prev parent reply other threads:[~2018-04-24 20:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:26 [PATCH 0/2] Fix file locking in EAL memory Anatoly Burakov
2018-04-19 12:26 ` [PATCH 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-24 14:06 ` Bruce Richardson
2018-04-19 12:26 ` [PATCH 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
2018-04-24 13:57 ` Bruce Richardson
2018-04-24 14:07 ` Bruce Richardson
2018-04-24 15:54 ` [PATCH v2 0/2] Fix file locking in EAL memory Anatoly Burakov
2018-04-24 15:54 ` [PATCH v2 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-24 15:54 ` [PATCH v2 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
2018-04-24 16:32 ` [PATCH v2 0/2] Fix file locking in EAL memory Stephen Hemminger
2018-04-24 17:25 ` Burakov, Anatoly
2018-04-24 20:05 ` Thomas Monjalon [this message]
2018-04-24 20:34 ` Stephen Hemminger
2018-04-25 10:36 ` [PATCH v3 " Anatoly Burakov
2018-04-25 10:36 ` [PATCH v3 1/2] mem: add memalloc init stage Anatoly Burakov
2018-04-25 10:36 ` [PATCH v3 2/2] mem: revert to using flock() and add per-segment lockfiles Anatoly Burakov
2018-04-28 9:38 ` Andrew Rybchenko
2018-04-30 8:29 ` Burakov, Anatoly
2018-04-30 11:31 ` Burakov, Anatoly
2018-04-30 11:51 ` Maxime Coquelin
2018-04-30 13:08 ` Andrew Rybchenko
2018-04-27 21:50 ` [PATCH v3 0/2] Fix file locking in EAL memory Thomas Monjalon
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=2542114.cvfhNbjQKQ@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.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 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.