From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Hiroshi Shimamoto <h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org,
Hayato Momma <h-momma-JhyGz2TFV9J8UrSeD/g0lQ@public.gmane.org>
Subject: Re: [memnic PATCH 5/5] pmd: handle multiple segments on xmit
Date: Thu, 27 Mar 2014 10:56:27 +0100 [thread overview]
Message-ID: <5190085.dvqKbtG10E@xps13> (raw)
In-Reply-To: <533304C6.2010009-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-03-26 17:48, Olivier MATZ:
> Hi Hiroshi-san,
>
> On 03/11/2014 06:40 AM, Hiroshi Shimamoto wrote:
> > From: Hiroshi Shimamoto <h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org>
> >
> > The current MEMNIC PMD cannot handle multiple segments.
> >
> > Add the functionality to transmit a mbuf which has multiple segments.
> > Walk every segment in transmitting mbuf and copy the data to MEMNIC
> > packet buffer.
> >
> > Signed-off-by: Hiroshi Shimamoto <h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.org>
> > Reviewed-by: Hayato Momma <h-momma-JhyGz2TFV9J8UrSeD/g0lQ@public.gmane.org>
>
> Reviewed-by: Olivier Matz <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Applied
> By the way, a similar patch could be done for the Linux driver
> but it's another story ;)
Yes another path is welcome
--
Thomas
prev parent reply other threads:[~2014-03-27 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 5:40 [memnic PATCH 5/5] pmd: handle multiple segments on xmit Hiroshi Shimamoto
[not found] ` <7F861DC0615E0C47A872E6F3C5FCDDBD01073B71-ZmjkEB1lVlLt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2014-03-26 16:48 ` Olivier MATZ
[not found] ` <533304C6.2010009-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-03-27 9:56 ` Thomas Monjalon [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=5190085.dvqKbtG10E@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=h-momma-JhyGz2TFV9J8UrSeD/g0lQ@public.gmane.org \
--cc=h-shimamoto-ehU+Cx/zZe18UrSeD/g0lQ@public.gmane.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.