mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Štefan Gula" <steweg@ynet.sk>
Cc: David Miller <davem@davemloft.net>,
	kaber@trash.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch v3, kernel version 3.2.1] Source mode for macvlan interface
Date: Wed, 25 Jan 2012 07:29:28 +0100	[thread overview]
Message-ID: <1327472968.14373.41.camel@edumazet-laptop> (raw)
In-Reply-To: <CAGsizzLHT6jK8zJn+5eJkTUt5NBdpK9uNHJTzDCPrbCcPBvBNA@mail.gmail.com>

Le mercredi 25 janvier 2012 à 07:22 +0100, Štefan Gula a écrit :

> It's a result of need to have enough space allocated for sk_buff
> struct before called macvlan_fill_info. I know that it looks somehow
> messy. BUt before the macvlan_fill_info is called there is only one
> procedure calcit. The problem of calcit is that it doesn't have access
> to struct net_device *dev int it. It has only access to struct sk_buff
> *skb, so from that point it cannot be called directly (whole parsing
> code had to be copied there to get the *dev a calling
> if_nlmsg_size(dev) from it. On the other hand calcit returns global
> static value of min_ifinfo_dump_size and that is shared among all
> interfaces and modifying like this do the job properly. There was
> another different way and that was creating and registering a whole
> new PF_MACLVAN netlink group resulting in copying almost 95% percent
> of given code and modified it somehow to do the same.
> 
> If it should be result of separate commitment than ok, but it was
> result apparently of need only for use of macvlan that's why it was
> included in my patch.
> 
> So how should I proceed with it?

A separate patch for this part, as David said ?

The intent is to catch people attention on a particular point, instead
of unnoticed code in some huge unrelated patch.




  reply	other threads:[~2012-01-25  6:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12446987.2261327416407141.JavaMail.root@5-MeO-DMT.ynet.sk>
2012-01-24 14:55 ` Stefan Gula
2012-01-25  4:03   ` David Miller
2012-01-25  6:22     ` Štefan Gula
2012-01-25  6:29       ` Eric Dumazet [this message]
2012-01-25  6:56         ` Štefan Gula

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=1327472968.14373.41.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steweg@ynet.sk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®