From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs_io: new functions
Date: Tue, 09 Oct 2012 16:53:49 -0500 [thread overview]
Message-ID: <50749CED.2070200@sgi.com> (raw)
In-Reply-To: <50748E38.4030303@sandeen.net>
On 10/09/12 15:51, Eric Sandeen wrote:
> On 10/9/12 3:47 PM, Mark Tinguely wrote:
>> On 10/09/12 14:07, Eric Sandeen wrote:
>>> On 9/24/12 4:51 PM, Mark Tinguely wrote:
>>>> On 07/25/12 17:30, Dave Chinner wrote:
>>>>> This is just a couple of additional functions for xfs_io I have had
>>>>> sitting around for a while. The first is an interface to
>>>>> sync_file_range() for better control of file writeback. The second
>>>>> and third introduce vectored pread/pwrite so that I could simulate
>>>>> the same style of vectored IO that KVM does via direct IO (hint -
>>>>> tracing indicated that the generic direct IO code doesn't handle
>>>>> this particularly efficiently).
>>>>>
>>>>> _____________________________________________
>>>>
>>>> This series has been committed to
>>>> git://oss.sgi.com/xfs/cmds/xfsprogs.git
>>>>
>>>> -Mark.
>>>>
>>>> _______________________________________________
>>>> xfs mailing list
>>>> xfs@oss.sgi.com
>>>> http://oss.sgi.com/mailman/listinfo/xfs
>>>>
>>>
>>> Looks like this might need some config-fu:
>>>
>>> pread.o: In function `do_pread':
>>> /src/git/xfsprogs/io/pread.c:198: undefined reference to `preadv'
>>> /src/git/xfsprogs/io/pread.c:198: undefined reference to `preadv'
>>> pwrite.o: In function `do_pwrite':
>>> /src/git/xfsprogs/io/pwrite.c:85: undefined reference to `pwritev'
>>> /src/git/xfsprogs/io/pwrite.c:85: undefined reference to `pwritev'
>>> sync_file_range.o: In function `sync_range_f':
>>> /src/git/xfsprogs/io/sync_file_range.c:87: undefined reference to `sync_file_range'
>>>
>>>
>>> (on a Centos5 box)
>>
>>
>> Thanks Eric, I will take a look at it.
>
> I actually started (sorry, should have just done it before sending the mail)
>
> I'll take care of it, I'm halfway there.
>
> -Eric
>
>> --Mark.
>>
>
Excellent. That is easy!
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-10-09 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:30 [PATCH 0/3] xfs_io: new functions Dave Chinner
2012-07-25 22:30 ` [PATCH 1/3] xfs_io: add sync_file_range support Dave Chinner
2012-07-28 23:56 ` Christoph Hellwig
2012-07-25 22:30 ` [PATCH 2/3] xfs_io: implement preadv for vectored reads Dave Chinner
2012-07-28 23:57 ` Christoph Hellwig
2012-08-09 20:08 ` Mark Tinguely
2012-07-25 22:30 ` [PATCH 3/3] xfs_io: implement pwritev for vectored writes Dave Chinner
2012-07-28 23:57 ` Christoph Hellwig
2012-09-24 21:51 ` [PATCH 0/3] xfs_io: new functions Mark Tinguely
2012-10-09 19:07 ` Eric Sandeen
2012-10-09 20:47 ` Mark Tinguely
2012-10-09 20:51 ` Eric Sandeen
2012-10-09 21:53 ` Mark Tinguely [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=50749CED.2070200@sgi.com \
--to=tinguely@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox