DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: John Levon <john.levon@nutanix.com>,
	 "dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
	 "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] eal: allow hugetlbfs sub-directories
Date: Tue, 12 Oct 2021 14:38:48 +0200	[thread overview]
Message-ID: <CAJFAV8xQMdXRergCKZPUR6FdKkap=eynhr6fX_dYpvozRGxDBw@mail.gmail.com> (raw)
In-Reply-To: <YRwWfPNzqzLG+HdI@movementarian.org>

On Tue, Aug 17, 2021 at 10:05 PM John Levon <john.levon@nutanix.com> wrote:
> On Mon, Aug 09, 2021 at 12:24:34PM +0100, John Levon wrote:
>
> > get_hugepage_dir() was implemented in such a way that a --huge-dir
> > option had to exactly match the mountpoint, but there's no reason for
> > this restriction: DPDK might not be the only user of hugepages, and
> > shouldn't assume it owns an entire mountpoint. For example, if I have
> > /dev/hugepages/myapp, and /dev/hugepages/dpdk, I should be able to
> > specify:
> >
> > --huge-dir=/dev/hugepages/dpdk/
> >
> > and have DPDK only use that sub-directory.
> >
> > Fix the implementation to allow a sub-directory within a suitable
> > hugetlbfs mountpoint to be specified, preferring the closest match.
> >
> > Signed-off-by: John Levon <john.levon@nutanix.com>
> > ---
> > v2: prefer closer matches
> > v3: checkpatch fixes
> > v4: fix docs, added tests
>
> Anyone like to (re) review?

Your patch lgtm, I tested a few scenarios I had in mind and it looks ok.
Dmitry offered to rebase after your patch, can you send a new revision
with following updates?
- This patch only concerns Linux, so the title prefix should be eal/linux,
- Jerin asked for a release notes update, a quick description is fine,
- Dmitry mentionned he acked your v3, so you can add it.


Thanks.

-- 
David Marchand


  reply	other threads:[~2021-10-12 12:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 21:05 John Levon
2021-06-25 10:44 ` [dpdk-dev] [PATCH RESEND] " John Levon
2021-07-06  9:43   ` David Marchand
2021-07-07 20:06   ` Dmitry Kozlyuk
2021-07-07 21:58     ` John Levon
2021-07-08  9:36     ` [dpdk-dev] [PATCH] " John Levon
2021-07-08  9:36       ` John Levon
2021-07-08 10:59     ` [dpdk-dev] [PATCH v3] " John Levon
2021-07-15 22:37       ` Dmitry Kozlyuk
2021-07-22 20:29       ` David Marchand
2021-07-22 21:06         ` John Levon
2021-07-23  7:29           ` Thomas Monjalon
2021-08-09 11:24             ` [dpdk-dev] [PATCH] " John Levon
2021-08-09 13:45               ` Jerin Jacob
2021-08-17 20:05               ` John Levon
2021-10-12 12:38                 ` David Marchand [this message]
2021-10-12 16:05                   ` [dpdk-dev] [PATCH] eal/linux: " John Levon
2021-10-12 19:03                     ` David Marchand
2021-10-12 19:58                       ` John Levon

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='CAJFAV8xQMdXRergCKZPUR6FdKkap=eynhr6fX_dYpvozRGxDBw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=john.levon@nutanix.com \
    --cc=thomas@monjalon.net \
    /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).