Displaying 20 results from an estimated 200 matches similar to: "[PATCH v20 19/32] ocfs2: Provide a splice-read stub"
2023 May 20
3
[PATCH v21 22/30] ocfs2: Provide a splice-read stub
Provide a splice_read stub for ocfs2. This emits trace lines and does an
atime lock/update before calling filemap_splice_read(). Splicing from
direct I/O is handled by the caller.
A couple of new tracepoints are added for this purpose.
Signed-off-by: David Howells <dhowells at redhat.com>
cc: Christoph Hellwig <hch at lst.de>
cc: Al Viro <viro at zeniv.linux.org.uk>
cc: Jens
2013 Jul 25
0
[PATCH V8 21/33] ocfs2: add support for read_iter and write_iter
Signed-off-by: Dave Kleikamp <dave.kleikamp at oracle.com>
Acked-by: Joel Becker <jlbec at evilplan.org>
Cc: Zach Brown <zab at zabbo.net>
Cc: Mark Fasheh <mfasheh at suse.com>
Cc: ocfs2-devel at oss.oracle.com
---
fs/ocfs2/aops.h | 2 +-
fs/ocfs2/file.c | 55 ++++++++++++++++++++++----------------------------
fs/ocfs2/ocfs2_trace.h | 6 +++---
3 files
2013 Jan 09
0
[PATCH V5 19/30] ocfs2: add support for read_iter, write_iter, and direct_IO_bvec
From: Zach Brown <zab@zabbo.net>
ocfs2''s .aio_read and .aio_write methods are changed to take
iov_iter and pass it to generic functions. Wrappers are made to pack
the iovecs into iters and call these new functions.
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: Zach Brown <zab@zabbo.net>
Cc: Mark Fasheh <mfasheh@suse.com>
Cc: Joel Becker
2009 Jun 19
2
[PATCH] ocfs2: Update atime in splice read if necessary.
We should call ocfs2_inode_lock_atime instead of ocfs2_inode_lock
in ocfs2_file_splice_read like we do in ocfs2_file_aio_read so
that we can update atime in splice read if necessary.
Signed-off-by: Tao Ma <tao.ma at oracle.com>
---
fs/ocfs2/file.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
index 775ac34..95cba48 100644
2013 Sep 03
1
[PATCH V3 RESENT] ocfs2: lighten up allocate transaction
Hi Andrew Morton,
The patch "[patch 05/22] ocfs2: lighten up allocate transaction" in mm tree
is not the newest one, please drop it from mm tree. This patch V3 is newest,
please replace it. Thanks.
The issue scenario is as following:
When fallocating a very large disk space for a small file,
__ocfs2_extend_allocation attempts to get a very large transaction.
For some journal
2023 May 28
1
[PATCH 1/2] ocfs2: correct return value of ocfs2_local_free_info()
Now in ocfs2_local_free_info(), it returns 0 even if it actually fails.
Though it doesn't cause any real problem since the only caller
dquot_disable() ignores the return value, we'd better return correct
as it is.
Signed-off-by: Joseph Qi <joseph.qi at linux.alibaba.com>
---
fs/ocfs2/quota_local.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git
2014 Nov 13
0
[PATCH 52/56] drivers/char/virtio: support compiling out splice
On Thu, Nov 13, 2014 at 10:23:29PM +0100, Pieter Smith wrote:
> Compile out splice support from virtio character driver when the splice-family
> of syscalls is not supported by the system (i.e. CONFIG_SYSCALL_SPLICE is
> undefined).
>
> Signed-off-by: Pieter Smith <pieter at boesman.nl>
> ---
> drivers/char/virtio_console.c | 4 +++-
> 1 file changed, 3
2014 Nov 13
1
[PATCH 52/56] drivers/char/virtio: support compiling out splice
Compile out splice support from virtio character driver when the splice-family
of syscalls is not supported by the system (i.e. CONFIG_SYSCALL_SPLICE is
undefined).
Signed-off-by: Pieter Smith <pieter at boesman.nl>
---
drivers/char/virtio_console.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index
2014 Nov 13
1
[PATCH 52/56] drivers/char/virtio: support compiling out splice
Compile out splice support from virtio character driver when the splice-family
of syscalls is not supported by the system (i.e. CONFIG_SYSCALL_SPLICE is
undefined).
Signed-off-by: Pieter Smith <pieter at boesman.nl>
---
drivers/char/virtio_console.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index
2012 Apr 14
0
[LLVMdev] splice problem
Hi all and thank you in advance.
I have problem connected with to functions basic blocks list splice, I
have tried to splice list of basic blocks one function with another
and after delete it, I have replaced all uses of this function with
another, I have even tried splice basic blocks of copy of this
function, but it also does not help, I have got working byte code and
I have compiled it by help
2015 Jul 28
1
[LLVMdev] splice and undefined physical reg
Hi,
i have got some troubles while trying to instrumentate a indirect call
instruction.
Basically, every time i run into a CALL64r i would like to have this
situation:
------
| .... |
| CMP |
| JE |
------
| |
--- -----
| |
---- ----
2016 Oct 26
0
Too many references: cannot splice
Hi,
Could you please have a look at https://lkml.org/lkml/2016/2/2/538 and see
if this makes any sense to you? I've been checking kernel changes
between linux_3.16.7 and linux_3.16.36, and this has popped out. Could this
be the reason for the "too many references" errors?
Regards,
Luis Ugalde.
On Thu, Oct 13, 2016 at 3:47 PM, Luis Ugalde <forondarena at gmail.com> wrote:
2008 Jan 21
0
Obtaining Midas and splice index values in onechannelGUI
Hello,
I've meanwhile got onechannelGUI running (my OS is windows). I'm trying to
use it for the analysis of human exon arrays. I was able to load cel files
and run them through affymetrix power tools, to obtain normalized affy data.
My next step was trying to find differentially spliced exons. The menu
offers to calculate either Midas or splice index scores. However, when I try
to use
2015 Jul 28
1
[LLVMdev] Splice and undefined physical reg
Hi,
i have got some troubles while writing an X86 machine pass to instrumentate
indirect calls .
Basically, every time i run into a CALL64r i would like to have this
situation:
------
| .... |
| CMP |
| JE |
------
| |
--- -----
| |
----
2016 Oct 26
1
Too many references: cannot splice
On 26 Oct 2016, at 11:14, Luis Ugalde <forondarena at gmail.com> wrote:
>
> Hi,
>
> Could you please have a look at https://lkml.org/lkml/2016/2/2/538 and see
> if this makes any sense to you? I've been checking kernel changes
> between linux_3.16.7 and linux_3.16.36, and this has popped out. Could this
> be the reason for the "too many references"
2016 Oct 13
2
Too many references: cannot splice
Hi,
A while ago I sent an email regarding these "*ETOOMANYREFS* Too many
references: cannot splice." that we've seen since Debian updated the Jessie
kernel to
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64
while older kernels, like 3.16.0-4-amd64 #1 SMP Debian
3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 showed no errors at all.
I was wondering if no one
2005 Aug 25
1
'splice' two data frames
Hi,
I often need to take columns from two data.frames and 'splice' them
together (alternately taking a column from the first data frame, then
from the second). For example:
x <- table(sample(letters[1:9], 100, replace=TRUE),
sample(letters[1:4], 100, replace=TRUE))
y <- prop.table(x)
splice <- function (x, y) {
z <- matrix(rep(NA, (ncol(x) * 2) * nrow(x)), nrow
2017 Dec 19
0
[PATCH v20 0/7] Virtio-balloon Enhancement
On Tue, Dec 19, 2017 at 11:05:11PM +0900, Tetsuo Handa wrote:
> Removing exceptional path made this patch easier to read.
> But what I meant is
>
> Can you eliminate exception path and fold all xbitmap patches into one, and
> post only one xbitmap patch without virtio-balloon changes?
>
> .
>
> I still think we don't need xb_preload()/xb_preload_end().
> I
2017 Dec 19
0
[PATCH v20 0/7] Virtio-balloon Enhancement
On Tue, Dec 19, 2017 at 11:05:11PM +0900, Tetsuo Handa wrote:
> Wei Wang wrote:
> > ChangeLog:
> > v19->v20:
> > 1) patch 1: xbitmap
> > - add __rcu to "void **slot";
> > - remove the exceptional path.
> > 2) patch 3: xbitmap
> > - DeveloperNotes: add an item to comment that the current bit range
> > related APIs operating on
2017 Dec 20
0
[PATCH v20 0/7] Virtio-balloon Enhancement
On Wed, Dec 20, 2017 at 06:34:36PM +0800, Wei Wang wrote:
> On 12/19/2017 10:05 PM, Tetsuo Handa wrote:
> > I think xb_find_set() has a bug in !node path.
>
> I think we can probably remove the "!node" path for now. It would be good to
> get the fundamental part in first, and leave optimization to come as
> separate patches with corresponding test cases in the