All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: new statx extensions
Date: Mon, 24 Oct 2022 20:56:31 -0700	[thread overview]
Message-ID: <Y1deb+K15rKghuP9@sol.localdomain> (raw)
In-Reply-To: <CAH2r5muLCRn1O31yCJ=pemuYBY5JpW3NhOBeRpDDE5=-jcLLpQ@mail.gmail.com>

Hi Steve,

On Thu, Oct 20, 2022 at 10:24:22PM -0500, Steve French wrote:
> I saw this patch series relating to exposing DIO alignment information
> mentioned in lwn today
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=825cf206ed51
> 
> Do you have any ideas of whether any network filesystem could support
> this?  There are lots of features about the server filesystem and
> preferred i/o sizes etc. that can be sent over the protocol (for
> SMB3.1.1).
> 
> Looking at 6.1-rc1 - it looks like this was mainly for xfs and ext4
> but is there any reason that it would be beneficial for cifs.ko - and
> if so is there more clarification on what information would be needed
> from the server to set this value?
> 

STATX_DIOALIGN can, and should, be supported by any filesystem that supports
O_DIRECT.

Its scope is specifically direct I/O alignment restrictions.  It doesn't include
anything about the preferred I/O size.  Note that the existing field
"stx_blksize" is already documented to be the preferred I/O size.

If you have any more questions or thoughts about this, please bring them up on
linux-fsdevel@vger.kernel.org.  That's where all the STATX_DIOALIGN stuff has
been discussed.

- Eric

      reply	other threads:[~2022-10-25  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  3:24 new statx extensions Steve French
2022-10-25  3:56 ` Eric Biggers [this message]

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=Y1deb+K15rKghuP9@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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.