Hi Connor,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on fuse/for-next]
[also build test WARNING on linux/master linus/master v5.12 next-20210507]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
Distribute requests across the multiqueue complex automatically based
on the IRQ affinity.
Suggested-by: Stefan Hajnoczi
Signed-off-by: Connor Kuehl
---
fs/fuse/virtio_fs.c | 30 --
1 file changed, 24 insertions(+), 6 deletions(-)
diff --git a/fs/fuse/virtio_fs.c
Hi guys,
I have one question about adding two new virtqueues for dgram. One new
thought is that we don't add two new virtqueues but keep using existing
virtqueues for both stream and dgram.
At the beginning when I first thought about supporting dgram, I thought
adding two new virtqueues would be
On Fri, 7 May 2021 17:43:32 +0200
Stefano Garzarella wrote:
> >The start/stop of a seq_file() is made for taking locks. I do this with all
> >my code in ftrace. Yeah, there's a while loop between the two, but that's
> >just to fill the buffer. It's not that long and it never goes to userspace
>
On Fri, May 07, 2021 at 10:40:36AM -0400, Steven Rostedt wrote:
On Fri, 7 May 2021 16:11:20 +0200
Stefano Garzarella wrote:
Hi Steven,
On Wed, May 05, 2021 at 04:38:55PM -0400, Steven Rostedt wrote:
>The new trace-cmd 3.0 (which is almost ready to be released) allows for
>tracing between
On Fri, 7 May 2021 16:11:20 +0200
Stefano Garzarella wrote:
> Hi Steven,
>
> On Wed, May 05, 2021 at 04:38:55PM -0400, Steven Rostedt wrote:
> >The new trace-cmd 3.0 (which is almost ready to be released) allows for
> >tracing between host and guests with timestamp synchronization such that
>
Hi Steven,
On Wed, May 05, 2021 at 04:38:55PM -0400, Steven Rostedt wrote:
The new trace-cmd 3.0 (which is almost ready to be released) allows for
tracing between host and guests with timestamp synchronization such that
the events on the host and the guest can be interleaved in the proper order
