From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: fix how to calculate space left in a hugetlbfs
Date: Thu, 12 Nov 2015 18:49:30 +0100 [thread overview]
Message-ID: <2366990.hyhGG8iGNs@xps13> (raw)
In-Reply-To: <20151112093826.5f287608@xeon-e3>
2015-11-12 09:38, Stephen Hemminger:
> On Thu, 12 Nov 2015 08:17:57 +0800
> Jianfeng Tan <jianfeng.tan@intel.com> wrote:
>
> > This patch enables calculating space left in a hugetlbfs.
> > There are three sources to get the information: 1. from
> > sysfs; 2. from option size specified when mount; 3. use
> > statfs. We should use the minimum one of these three sizes.
> >
> > Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
>
> Thanks, the hugetlbfs usage up until now has been rather brute force.
> I wonder if long term it might be better to defer all this stuff
> to another library like libhugetlbfs.
> https://github.com/libhugetlbfs/libhugetlbfs
>
> Especially wen dealing with other architectures it might provide
> some nice abstraction.
Maybe, maybe not :)
Sergio arleady looked at it:
http://dpdk.org/ml/archives/dev/2015-July/022080.html
next prev parent reply other threads:[~2015-11-12 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 0:17 Jianfeng Tan
2015-11-12 2:10 ` [dpdk-dev] [PATCH v2] mem: " Jianfeng Tan
2015-11-12 13:14 ` Sergio Gonzalez Monroy
2015-11-12 7:48 ` [dpdk-dev] [PATCH] mem: fix how to " De Lara Guarch, Pablo
2015-11-12 1:57 ` [dpdk-dev] [PATCH v2] mem: " Jianfeng Tan
2015-11-12 17:38 ` [dpdk-dev] [PATCH] mem: fix how to " Stephen Hemminger
2015-11-12 17:49 ` Thomas Monjalon [this message]
2015-11-18 2:42 ` [dpdk-dev] [PATCH v3] mem: " Jianfeng Tan
2015-11-18 10:28 ` Sergio Gonzalez Monroy
2015-12-21 8:34 ` Qiu, Michael
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=2366990.hyhGG8iGNs@xps13 \
--to=thomas.monjalon@6wind.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).