From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Parav Pandit <parav@nvidia.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"jasowang@redhat.com" <jasowang@redhat.com>
Subject: Re: [iproute2-next v2 4/4] vdpa: Enable user to set mtu of the vdpa device
Date: Mon, 20 Dec 2021 18:06:08 -0500 [thread overview]
Message-ID: <20211220180507-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <8df990f1-7067-b336-f97a-85fe98882fb9@gmail.com>
On Mon, Dec 20, 2021 at 02:11:44PM -0700, David Ahern wrote:
> On 12/20/21 12:11 PM, Parav Pandit wrote:
> >> After consideration, this future proofing seems like a good thing to have.
> > Ok. I will first get kernel change merged, after which will send v3 for iproute2.
>
> this set has been committed; not sure what happened to the notification
> from patchworks bot.
OK in that case it's too late, so maybe let's worry about supporting
extensions later when we actually need them, in particular when linux
better supports mtu > 64k.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [iproute2-next v2 4/4] vdpa: Enable user to set mtu of the vdpa device
Date: Mon, 20 Dec 2021 18:06:08 -0500 [thread overview]
Message-ID: <20211220180507-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <8df990f1-7067-b336-f97a-85fe98882fb9@gmail.com>
On Mon, Dec 20, 2021 at 02:11:44PM -0700, David Ahern wrote:
> On 12/20/21 12:11 PM, Parav Pandit wrote:
> >> After consideration, this future proofing seems like a good thing to have.
> > Ok. I will first get kernel change merged, after which will send v3 for iproute2.
>
> this set has been committed; not sure what happened to the notification
> from patchworks bot.
OK in that case it's too late, so maybe let's worry about supporting
extensions later when we actually need them, in particular when linux
better supports mtu > 64k.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-12-20 23:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 8:08 [iproute2-next v2 0/4] vdpa tool to query and set config layout Parav Pandit
2021-12-17 8:08 ` Parav Pandit via Virtualization
2021-12-17 8:08 ` [iproute2-next v2 1/4] vdpa: Update kernel headers Parav Pandit
2021-12-17 8:08 ` Parav Pandit via Virtualization
2021-12-17 8:08 ` [iproute2-next v2 2/4] vdpa: Enable user to query vdpa device config layout Parav Pandit
2021-12-17 8:08 ` Parav Pandit via Virtualization
2021-12-17 8:08 ` [iproute2-next v2 3/4] vdpa: Enable user to set mac address of vdpa device Parav Pandit
2021-12-17 8:08 ` Parav Pandit via Virtualization
2021-12-17 8:08 ` [iproute2-next v2 4/4] vdpa: Enable user to set mtu of the " Parav Pandit
2021-12-17 8:08 ` Parav Pandit via Virtualization
2021-12-18 20:53 ` David Ahern
2021-12-18 20:53 ` David Ahern
2021-12-18 22:07 ` Michael S. Tsirkin
2021-12-18 22:07 ` Michael S. Tsirkin
2021-12-20 3:49 ` Parav Pandit
2021-12-20 3:49 ` Parav Pandit via Virtualization
2021-12-20 12:02 ` Michael S. Tsirkin
2021-12-20 12:02 ` Michael S. Tsirkin
2021-12-20 19:11 ` Parav Pandit
2021-12-20 19:11 ` Parav Pandit via Virtualization
2021-12-20 21:11 ` David Ahern
2021-12-20 21:11 ` David Ahern
2021-12-20 23:06 ` Michael S. Tsirkin [this message]
2021-12-20 23:06 ` Michael S. Tsirkin
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=20211220180507-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dsahern@gmail.com \
--cc=jasowang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux-foundation.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.