All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Using loff_t or u64 for PFL port
Date: Mon, 29 Oct 2018 09:23:04 +0000	[thread overview]
Message-ID: <8C539D08-D7F6-4B17-8A8D-01FEFF03BD2E@whamcloud.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1810290345010.6811@casper.infradead.org>

On Oct 28, 2018, at 21:49, James Simmons <jsimmons@infradead.org> wrote:
> 
> 
> While doing the PFL port I noticed a inconsistent use of loff_t and u64.
> While in Greg's branch several patches landed to make the prototypes
> match the function with changing any unmatching loff_t/u64 to use u64.
> I don't know if using u64 solely as the proper solution. What is the
> proper unit to use?

James, could you please clarify what part of the code you are referencing?

Cheers, Andreas
---
Andreas Dilger
Principal Lustre Architect
Whamcloud

  reply	other threads:[~2018-10-29  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29  3:49 [lustre-devel] Using loff_t or u64 for PFL port James Simmons
2018-10-29  9:23 ` Andreas Dilger [this message]
2018-10-29 15:18   ` James Simmons
2018-10-30 14:55     ` Patrick Farrell

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=8C539D08-D7F6-4B17-8A8D-01FEFF03BD2E@whamcloud.com \
    --to=adilger@whamcloud.com \
    --cc=lustre-devel@lists.lustre.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.