From: Carlos Llamas <cmllamas@google•com>
To: Stefano Garzarella <sgarzare@redhat•com>
Cc: Lee Jones <lee.jones@linaro•org>,
linux-kernel@vger•kernel.org, Ram Muthiah <rammuthiah@google•com>,
"Michael S. Tsirkin" <mst@redhat•com>,
Jason Wang <jasowang@redhat•com>,
Stefan Hajnoczi <stefanha@redhat•com>,
"David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
virtualization@lists•linux-foundation.org, kvm@vger•kernel.org,
netdev@vger•kernel.org, jiang.wang@bytedance•com
Subject: Re: [PATCH 1/1] virtio/vsock: Make vsock virtio packet buff size configurable
Date: Fri, 9 Dec 2022 19:48:02 +0000 [thread overview]
Message-ID: <Y5OQ8jQsK2Dz8tPy@google.com> (raw)
In-Reply-To: <20210722125519.jzs7crke7yqfh73e@steredhat>
On Thu, Jul 22, 2021 at 02:55:19PM +0200, Stefano Garzarella wrote:
> >
> > +uint virtio_transport_max_vsock_pkt_buf_size = 1024 * 64;
> > +module_param(virtio_transport_max_vsock_pkt_buf_size, uint, 0444);
> > +EXPORT_SYMBOL_GPL(virtio_transport_max_vsock_pkt_buf_size);
> > +
I'm interested on this functionality, so I could take this on.
>
> Maybe better to add an entry under sysfs similar to what Jiang proposed
> here:
> https://lists.linuxfoundation.org/pipermail/virtualization/2021-June/054769.html
Having a look at Jiang's RFC patch it seems the proposed sysfs node
hangs off from the main kernel object e.g. /sys/kernel. So I wonder if
there is a more appropriate parent for this knob?
Also, I noticed that Ram's patch here is using read-only permissions for
the module parameter and switching to sysfs would mean opening this knob
up to be dynamically configured? I'd need to be careful here.
--
Carlos Llamas
next prev parent reply other threads:[~2022-12-09 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 14:30 [PATCH 1/1] virtio/vsock: Make vsock virtio packet buff size configurable Lee Jones
2021-07-22 12:55 ` Stefano Garzarella
2022-12-09 19:48 ` Carlos Llamas [this message]
2022-12-12 13:10 ` Stefano Garzarella
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=Y5OQ8jQsK2Dz8tPy@google.com \
--to=cmllamas@google$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jasowang@redhat$(echo .)com \
--cc=jiang.wang@bytedance$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rammuthiah@google$(echo .)com \
--cc=sgarzare@redhat$(echo .)com \
--cc=stefanha@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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