From: Eric Barton <eeb@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] discontiguous kiov pages
Date: Thu, 2 Jun 2011 14:19:14 +0100 [thread overview]
Message-ID: <002c01cc2127$ac5b7da0$051278e0$@com> (raw)
In-Reply-To: <4DE6F67B.6040207@cray.com>
Wang,
Inline...
> -----Original Message-----
> From: lustre-devel-bounces at lists.lustre.org [mailto:lustre-devel-bounces at lists.lustre.org] On Behalf
> Of wang
> Sent: 02 June 2011 3:34 AM
> To: lustre-devel at lists.lustre.org
> Subject: [Lustre-devel] discontiguous kiov pages
>
> Our gnilnd is running into a hole in kiov list in Lustre 2.1:
>
> LustreError: 17837:0:(gnilnd_cb.c:594:kgnilnd_setup_phys_buffer()) Can't make payload
> contiguous in I/O VM:page 17, offset 0, nob 6350, kiov_offset 0 kiov_len 2254
> LustreError: 17837:0:(gnilnd_cb.c:1751:kgnilnd_send()) unable to setup buffer: -22
>
> Is it now legal for an internal IOV (or KIOV) page to have less than a full page size ?
>
> It used to be that only the first and last page in an IOV were allowed
> to be of a offset + length < PAGE_SIZE.
Quite correct. LNDs have relied on this for years now.
A change like this should not have occurred without discussion
about the wider impact.
> It doesn't have this problem with 1.8 client and 2.1 server.
>
> Wally
>
>
>
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
next prev parent reply other threads:[~2011-06-02 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 2:33 [Lustre-devel] discontiguous kiov pages wang
2011-06-02 13:19 ` Eric Barton [this message]
2011-06-07 23:57 ` Oleg Drokin
2011-06-08 16:08 ` Nic Henke
2011-06-08 20:09 ` Jinshan Xiong
2011-06-09 8:37 ` Peter Jones
2011-06-09 3:16 ` Oleg Drokin
2011-06-09 14:38 ` Eric Barton
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='002c01cc2127$ac5b7da0$051278e0$@com' \
--to=eeb@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.