From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Fu, Siyuan" <siyuan.fu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Jiaxin" <jiaxin.wu@intel.com>,
"Ye, Ting" <ting.ye@intel.com>
Subject: Re: Plan to move all network components to NetworkPkg
Date: Mon, 5 Nov 2018 02:21:43 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BEF0D71@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <B1FF2E9001CE9041BD10B825821D5BC58B67B0B7@SHSMSX103.ccr.corp.intel.com>
Siyuan,
This is a good idea. Will the driver name be changed after the location change? Or as Liming suggested, maybe you could provide a text format directory tree layout to show what the final NetworkPkg is like.
Thanks/Ray
From: Fu, Siyuan
Sent: Friday, November 2, 2018 4:10 PM
To: edk2-devel@lists.01.org
Cc: Zeng, Star <star.zeng@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Ni, Ruiyu <ruiyu.ni@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>; Ye, Ting <ting.ye@intel.com>
Subject: Plan to move all network components to NetworkPkg
Hi, All
The edk2 Bugzilla #1278 "Delete IPv4 only TCP/iSCSI/PXE drivers in MdeModulePkg" has been confirmed to be included in edk2-stable201903 tag, so platform DSC/FDF need to be updated to adopt the change by that time. I think might be an opportunity moment to make a little more - move all edk2 network related drivers/libraries into one single package - that what we want to do for a long time.
In current edk2, the network stack components are located mainly in 2 different places, the MdeModulePkg and NetworkPkg, due to some historical reasons. The MdeModulePkg contains most of the IPv4 stack drivers (in MdeModulePkg/Universal/Network directory), and all the network libraries. The NetworkPkg contains all the IPv6 stack drivers and also some dual stack drivers (like TcpDxe). The PCDs related to network configuration are also defined in different packages: PcdTftpBlockSize is in MdeModulePkg.dec and others are in NetworkPkg.dec. There are also drivers in these 2 packages have a same name (like UefiPxeBcDxe).
We can see these codes are not well organized, so I'd like to take this opportunity to change this situation, to move all network components to NetworkPkg, which will make the edk2 network stack code easier to use and maintain in the future.
I have created Bugzilla #1293 for this proposal, and I will send some patches for the detail changes. I hope it could be done together with #1278 so the platform only need to update their DSC/FDF file for one time. Please let me know if you have any comments on this, thanks.
https://bugzilla.tianocore.org/show_bug.cgi?id=1293
BestRegards
Fu Siyuan
next prev parent reply other threads:[~2018-11-05 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 8:10 Plan to move all network components to NetworkPkg Fu, Siyuan
2018-11-02 14:26 ` Gao, Liming
2018-11-05 2:21 ` Ni, Ruiyu [this message]
2018-11-05 5:26 ` Zeng, Star
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-list 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=734D49CCEBEEF84792F5B80ED585239D5BEF0D71@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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